BuildBase Console MCP server
Commit Nov 12, 2026Lets an AI agent manage BuildBase organizations, members, content, workflows, and settings using your existing account permissions.
Also known as buildbase-app/mcp, mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.0
- Last commit
- Nov 12, 2026
- License
- MIT
What is BuildBase Console MCP?
BuildBase Console lets an AI agent manage BuildBase organizations, members, content, workflows, and settings using your existing account permissions.
Summary generated from the project's README
About BuildBase Console MCP server
Managing BuildBase organizations, members, and workflows through an AI agent is what this server enables. It allows developers to interact with their existing accounts to read or modify console data, manage content, and configure settings. The agent operates within your existing role and permissions, meaning it can only perform actions that you are authorized to do yourself.
Setup is handled via OAuth through a browser-based sign-in process, requiring no manual API key generation or local installation. It works with various clients including Claude Code, Cursor, and VS Code with GitHub Copilot. The server uses a streamable HTTP transport to connect your AI client to the BuildBase console.
Security is managed at the organization level where owners can set access to off, read only, or read and write. For sensitive operations like destructive changes, member updates, or moving money, the agent must ask for your explicit approval in the chat. The system also uses blueprints to describe and apply organization setups from files.
What you can do with it
- 1Provision new organizationsAsk the agent to set up a new organization using a predefined blueprint file.
- 2Audit organization membershipRequest a list of all current organizations associated with your account.
- 3Modify console dataInstruct the agent to update specific content or settings within your workspace.
- 4Access developer documentationSearch for technical guides or environment templates to assist with SDK development.
Written from the project's README. Every use case is checked against a quote from it.
How to install BuildBase Console MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall BuildBase Console MCP in Claude Code
$ claude mcp add --transport http mcp https://api.console.buildbase.app/mcpInstall BuildBase Console MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://api.console.buildbase.app/mcp"
}
}
}Install BuildBase Console MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "http",
"url": "https://api.console.buildbase.app/mcp"
}
}
}Install BuildBase Console MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"http","url":"https://api.console.buildbase.app/mcp"}'Install BuildBase Console MCP in Codex
$ codex mcp add mcp --url https://api.console.buildbase.app/mcpInstall BuildBase Console MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] url = "https://api.console.buildbase.app/mcp"
Install BuildBase Console MCP in Gemini CLI
$ gemini mcp add -s user --transport http mcp https://api.console.buildbase.app/mcpInstall BuildBase Console MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"url": "https://api.console.buildbase.app/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablebuildbase-app/mcp is public and reachablegithub.com/buildbase-app/mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/buildbase-app/mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubBuildBase 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 to install, 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
Every client signs in the same way: it opens the BuildBase sign-in page in your browser, you sign in and approve. Guides for other clients are in docs/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 in Console > Account > Security: off, read only (the default) or read and write. The agent acts as the signed-in person, within that person's role. Deleting things, changing members or roles, moving money and changing sign-in settings ask for the person's approval in the chat first. Secrets are never returned 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 follow llms-install.md.
Troubleshooting
-
401 or "unauthorized": sign in again. In Claude Code run
/mcp, in Codexcodex mcp login buildbase, in Gemini CLI/mcp auth buildbase. Other clients have a sign-in or authenticate action on the server. -
"Agent access is off": an owner or admin of that organization turns it on in Console > Account > Security.
-
The agent can read but not change anything: the organization allows read 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 role in that organization allows.
-
The client cannot sign in: the client must support OAuth for remote servers. 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 dynamic client registration.
Cline's docs describe OAuth sign-in for the Cline CLI only. If the Cline editor extension cannot sign in, use the CLI.
- Claude Desktop's
Still stuck? Open a connection problem issue. Never paste a token or password.
Links
- Docs: docs.buildbase.app/console/ai-agents
- Privacy: www.buildbase.app/legal/privacy
- Terms: www.buildbase.app/legal/terms
- Support: support@buildbase.app or www.buildbase.app/contact
- Security: SECURITY.md
- Maintainers: MAINTENANCE.md covers publishing to the MCP Registry, the signing key, repository settings and setting up a repository like this one from scratch.
License
The files in this repository are under the MIT License. The BuildBase service itself is governed by the BuildBase Terms.
BuildBase Console MCP questions
How do I add BuildBase Console MCP to Claude Code?
Run claude mcp add --transport http mcp https://api.console.buildbase.app/mcp in your terminal. Add --scope user to make it available in every project.
How do I add BuildBase Console MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Can the AI agent delete my data or change my settings?
The agent acts within your specific role, and destructive changes like deleting things or changing members require your explicit approval in the chat first.
What if the agent is unable to change anything in my organization?
This usually means the organization's security settings are set to read-only; an owner or admin can change this to read and write in the security settings.
How can I control what the AI agent is allowed to do?
Access levels (off, read only, or read and write) are set per organization by owners and admins in the Security section of the Console.