Back to Browse

Console MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Manage BuildBase organizations, members, content, email, workflows and settings as yourself.

About

Manage BuildBase organizations, members, content, email, workflows and settings as yourself.

Remote endpoints: streamable-http: https://api.console.buildbase.app/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

file_system

Applies to the server that hosts this plugin, not to your machine.

HTTP Network Access

Connects to external APIs or services over the internet.

Shell Command Execution

Runs commands on the server that hosts it, not on your machine.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "app-buildbase-console": {
      "url": "https://api.console.buildbase.app/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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.

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

GroupToolsPurpose
Accountwhoami, list_orgs, open_orgWho you are, your organizations, pick one
Console readsconsole_catalog, console_getDiscover and read console data
Console changesconsole_write, console_destructive_changeChange data; destructive changes need approval
New organizationcreate_org, claim_linkCreate an organization, get a claim link
Blueprintsblueprint_schema, blueprint_validate, blueprint_plan, blueprint_export, blueprint_applyDescribe an org setup as a file, check it, plan it, apply it
Developer helpsearch_docs, fetch_doc, get_env_templateDocs search and env templates for building with the SDK
Exportsstart_export, get_export_statusExport 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.

Links

License

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

Reviews

No reviews yet

Be the first to review this server!