beam-logo

Build on Beam with your coding agent

One command to get started.

$curl -fsSL beam.cloud/agents.sh | sh

Installs the Beam CLI and the use-beam skill, and registers Beam's MCP server with every agent on your machine. No account needed yet: sign in afterwards with one click, from the terminal or from your agent.

Read the agent briefing ⟶Agent directory

Deploy to Beam from the agent you already use

One setup command registers Beam's MCP server with every supported agent it finds. Each card shows the per-agent command if you'd rather do one at a time.

Cursor

Cursor · IDE

AI-first editor. Agent mode uses MCP tools directly, so Beam shows up alongside your codebase.

  • Agent mode with MCP tools
  • Background agents
  • Per-project or global MCP config
beam mcp install --client cursor

Claude Code

Anthropic · Terminal

Agentic coding in your terminal. Runs the Beam CLI itself and calls the MCP server for state.

  • Runs beam deploy and beam logs directly
  • MCP tools for apps, logs, and metrics
  • Project-scoped .mcp.json config
beam mcp install --client claude-code

Codex

OpenAI · Terminal

OpenAI's terminal agent. Beam registers as an MCP server in ~/.codex/config.toml.

  • Command execution and file edits
  • MCP over Streamable HTTP
  • Runs the Beam CLI in its sandbox
beam mcp install --client codex

Windsurf

Codeium · IDE

Agentic IDE with Cascade. Beam's MCP tools become available to every Cascade session.

  • Cascade agent with MCP tools
  • Multi-file edits
  • Global MCP config
beam mcp install --client windsurf

Claude Desktop

Anthropic · Desktop

Chat with your workspace: deployments, logs, and metrics as MCP tools, bridged over stdio.

  • Read logs, metrics, and request stats
  • Deploy and roll back from chat
  • Manage secrets and databases
beam mcp install --client claude-desktop

Any MCP client

Streamable HTTP · IDE, Terminal, Desktop

Anything that speaks MCP over HTTP: point it at the server URL with a bearer token.

  • Stateless JSON-RPC, one POST per call
  • Bearer token auth
  • Docs MCP needs no token
https://app.beam.cloud/api/v1/mcp · Authorization: Bearer <token>

Docs server, no token: https://docs.beam.cloud/mcp

Infrastructure an agent can actually drive

Sandboxes for untrusted code

Isolated environments that boot in seconds. Run what the agent wrote, then throw it away or snapshot it.

Sub-second cold starts

Memory snapshots restore containers, GPUs included, fast enough for tool calls.

GPUs on demand

A10G to H100 on any app with one argument. Pay by the second while it runs.

Persistent state

Durable disks, shared volumes, and managed Postgres, Redis, MySQL, and MongoDB.

MCP and CLI access

Every dashboard operation as an MCP tool, and a CLI for anything that touches local files.

Any container image

A Dockerfile or a public image becomes a persistent service with a URL, disks, and secrets.

Logs and metrics

Container logs, CPU and GPU metrics, and request stats over MCP, so agents debug with evidence.

Versioned, reversible

Every deploy is a version. Rolling back is one call; stopping a bad one is another.

Pay as you gobilled by the millisecond

Start shipping on infra
you won’t outgrow.

Run sandboxes and GPU workloads on your cloud, and scale out to ours when you need to. No infra to manage.

Start BuildingRead the docs