Skip to main content
Glama

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.

check MCP Badge

Endpoint

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

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

Related MCP server: Mixedlane MCP Server

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

Add BuildBase to 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 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

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 Codex codex 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.

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

License

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to author and manage workflows, agents, tools, skills, policies, and reference docs in an Axonity tenant via the public REST API, with guardrails preventing direct publishing and secret exposure.
      100
      541 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to look up stored logins by URL, name, or alias and use them without seeing the secrets, injecting authentication into HTTP requests, running commands with credentials in the environment and scrubbed output, and fetching 2FA codes, subject to per-credential policies and user approval.
      23
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to browse organizations, networks, devices and connected clients, read switch ports, SSIDs, RF profiles, firewall rules and VPN settings, and — when an operator permits in read-only-off mode with explicit confirmation — change them or call any other Dashboard API endpoint. Credentials arrive per request as headers, nothing is stored, and every change is refused by default.
      Apache 2.0