Set up beam.page
Setup's the fiddly bit — a couple of minutes the first time, then it's just there. Paste this into your AI client, sign in with Google, done.
https://api.beam.page/mcpChatGPT
Plus / Pro / Business / EnterpriseNeeds a paid plan — Developer Mode for custom connectors isn't available on the free tier.
- In Settings, turn on Developer mode. Nothing below appears until you do.
- Open Plugins and click the +. Name it
beam.page, paste the URL, set Authentication to OAuth, and save. - Sign in with Google.
- In a chat: + → More → beam.page. Say "build me a website for…"
https://api.beam.page/mcpClaude (claude.ai or Claude Desktop)
the web version works from any browserClaude Desktop also reads files straight off your computer — handy for batches of photos, PDFs, or menus.
- Customize → Connectors → + → Add custom connector.
- Name it
beam.page, paste the URL, click Add. - Sign in with Google.
- In a new chat: + → Connectors → beam.page. Say "build me a website for…"
https://api.beam.page/mcpClaude Free is limited to one custom connector. Team / Enterprise workspaces need an owner to add it once at Organization level first.
Cursor
AI-native editorVS Code fork with native MCP. Free tier works fine — no Pro needed.
- Settings → Tools & MCP → New MCP Server, or edit
~/.cursor/mcp.jsondirectly. - Paste the config below, save.
- First tool call pops a browser for the Google sign-in.
{
"mcpServers": {
"beam-page": {
"url": "https://api.beam.page/mcp"
}
}
}If Cursor won't connect with the bare url field, swap the inner block for the mcp-remote shim — "command": "npx", "args": ["-y", "mcp-remote", "https://api.beam.page/mcp"].
Windsurf
Cascade — CodeiumCursor's closest cousin. Same JSON shape, slightly different field name.
- In the Cascade chat, click the MCP servers (hammer) icon → Configure → View raw config.
- Paste the config below into
~/.codeium/windsurf/mcp_config.json, save. - Click Refresh back in the Manage Plugins tab. First tool call pops a browser for Google sign-in.
{
"mcpServers": {
"beam-page": {
"serverUrl": "https://api.beam.page/mcp"
}
}
}Field is serverUrl, not url — easy to miss when copying from Cursor. If an older Windsurf build won't connect, fall back to the universal mcp-remote shim.
Claude Code
terminal — AnthropicTerminal agent. Full filesystem access and scriptable from the shell.
claude mcp add --transport http --scope user beam-page https://api.beam.page/mcpFirst time you use a beam.page tool, Claude Code opens a browser for the Google login automatically. Drop --scope user to install in the current directory only.
Codex CLI
terminal — OpenAIOpenAI's terminal agent. Same filesystem + shell ergonomics as Claude Code.
codex mcp add beam-page --url https://api.beam.page/mcpCodex prompts you to sign in with Google via your browser the first time you use it. If the prompt doesn't appear, run codex mcp login beam-page.
On Windows, Codex has a known bug with MCP sign-ins. It saves the login to Windows Credential Manager and then can't read it back, so it works for about an hour and then stops — usually with no Authenticate option to click, because Codex thinks it's still signed in. Removing and re-adding the server doesn't clear it, and neither does codex mcp logout reliably.
The workaround is to stop using the credential store. Add mcp_oauth_credentials_store = "file" to config.toml in your .codex folder and sign in again. Be aware that writes the token to a plain text file readable by anything running as you — fine on your own machine, worth a thought on a work one. It's an open Codex issue, not something we can fix from our side. If you'd rather not touch config files, use ChatGPT or Claude instead — both sign in through the browser and aren't affected.
Antigravity
CLI + desktop — GoogleGoogle's agent — CLI and 2.0 desktop app, sharing the same engine. Free for personal Gmail accounts in preview.
- Create
~/.gemini/config/mcp_config.jsonand paste the config below, save. - Run
agyin your terminal, then type/mcpand click the auth prompt. - Complete the Google sign-in in the browser. That's it.
{
"mcpServers": {
"beam-page": {
"serverUrl": "https://api.beam.page/mcp"
}
}
}Once this is done, the Antigravity 2.0 desktop app works too — no extra setup. It shares the same MCP config and Google sign-in.
Any MCP-compatible client should work in principle — but setup paths, JSON field names (url, serverUrl, and others), and OAuth handling all differ by client. Paste the connector URL below into your client's MCP settings, and check the client's MCP docs if you hit issues. The mcp-remote shim is the universal fallback when a remote HTTP connection won't take. And if it still won't, give us a shout — we'll have a go at making it work.
https://api.beam.page/mcp
Also listed on Smithery — for a one-line install in compatible clients:
npx -y smithery mcp add lola2-limited/beampage