BuildBase MCP server

Work in the BuildBase console as yourself: read and change your organizations, members, content, email, workflows and settings, and set an organization up from a blueprint, within your role and what each organization allows AI agents to do.

Endpoint

https://api.console.buildbase.app/mcp

Streamable HTTP. Sign in with your BuildBase account (OAuth). Nothing toinstall, no API key.

Quick start

Claude Code

claude mcp add --transport http buildbase https://api.console.buildbase.app/mcp

Then run /mcp in Claude Code and sign in. Or install the plugin:/plugin marketplace add buildbase-app/mcp, then/plugin install buildbase@buildbase.

Cursor

VS Code with GitHub Copilot

Install BuildBase in VS Code

Every client signs in the same way: it opens the BuildBase sign-in page in yourbrowser, you sign in and approve. Guides for other clients are indocs/clients.

First prompt to try

List my BuildBase organizations.

What it can do

Group	Tools	Purpose
Account	`whoami`, `list_orgs`, `open_org`	Who you are, your organizations, pick one
Console reads	`console_catalog`, `console_get`	Discover and read console data
Console changes	`console_write`, `console_destructive_change`	Change data; destructive changes need approval
New organization	`create_org`, `claim_link`	Create an organization, get a claim link
Blueprints	`blueprint_schema`, `blueprint_validate`, `blueprint_plan`, `blueprint_export`, `blueprint_apply`	Describe an org setup as a file, check it, plan it, apply it
Developer help	`search_docs`, `fetch_doc`, `get_env_template`	Docs search and env templates for building with the SDK
Exports	`start_export`, `get_export_status`	Export data

Access and safety

Agent access is set per organization by its owners and admins inConsole > Account > Security: off, read only (the default) or read andwrite. The agent acts as the signed-in person, within that person's role.Deleting things, changing members or roles, moving money and changing sign-insettings ask for the person's approval in the chat first. Secrets are neverreturned to the agent.

Clients

Client	Guide
Claude (claude.ai, Claude Desktop, Claude Code)	docs/clients/claude.md
ChatGPT	docs/clients/chatgpt.md
Codex	docs/clients/codex.md
Cursor	docs/clients/cursor.md
VS Code and GitHub Copilot	docs/clients/vscode.md
Gemini CLI	docs/clients/gemini-cli.md
Cline	docs/clients/cline.md
Lovable	docs/clients/lovable.md
v0	docs/clients/v0.md
Raycast	docs/clients/raycast.md
Any other client	docs/clients/other.md

AI agents installing the server for someone can followllms-install.md.

Troubleshooting

401 or "unauthorized": sign in again. In Claude Code run /mcp, inCodex codex mcp login buildbase, in Gemini CLI /mcp auth buildbase. Otherclients have a sign-in or authenticate action on the server.
"Agent access is off": an owner or admin of that organization turns iton in Console > Account > Security.
The agent can read but not change anything: the organization allowsread only. An owner or admin can switch it to read and write.
A tool is refused for your role: the agent can do only what your rolein that organization allows.
The client cannot sign in: the client must support OAuth for remoteservers. These cannot connect directly:
- Claude Desktop's claude_desktop_config.json, which is for local servers.Add BuildBase under Connectors instead.
- Clients that run only local (stdio) servers.
- Clients that support only client ID metadata documents and not dynamicclient registration.
Cline's docs describe OAuth sign-in for the Cline CLI only. If the Clineeditor extension cannot sign in, use the CLI.

Still stuck? Open a connection problemissue. Never paste a token or password.

License

The files in this repository are under the MIT License. TheBuildBase service itself is governed by theBuildBase Terms.

BuildBase MCP server