Skip to content
BuildBase
BuildBase in your AI tools

Use BuildBase in Zed

BuildBase in your AI tools: connect Zed to BuildBase's own MCP server and manage your BuildBase organization from Zed. You sign in as yourself, and Zed can do only what your role and your organization allow.

Add BuildBase to Zed

The address is the same in every AI tool: https://api.console.buildbase.app/mcp. BuildBase signs you in the first time Zed connects.

  1. In Zed, add a remote MCP server: Settings > AI > MCP Servers > Add Server > Add Remote Server. Use the address https://api.console.buildbase.app/mcp, or the command or config below.
  2. Sign in. With no Authorization header set, Zed runs the standard MCP sign-in and asks you to sign in.
  3. On BuildBase's sign-in page, sign in as you do to the console, then approve the consent screen, which names Zed and what it asks for.
  4. Ask Zed something, such as "List my BuildBase organizations."
settings.jsonJSON
{
  "context_servers": {
    "buildbase-console": {
      "url": "https://api.console.buildbase.app/mcp"
    }
  }
}

The plan it needs

Zed's MCP page does not name a plan.

How sign-in looks in Zed

With no Authorization header set, Zed runs the standard MCP sign-in and asks you to sign in.

What is different in Zed

  • agent.tool_permissions sets confirm, allow or deny, by default or per tool, as mcp:<server>:<tool>.
  • BuildBase adds its own rules on top: each organization is Off, Read only or Read and change for AI agents (Read only by default), and deletes, member and role changes, sends and money moves need your approval in the chat.
  • For a job with nobody to sign in, send one of your organization's API keys as the bearer instead. Add headers, with Authorization: Bearer <key>, to the server under context_servers; Zed then skips the sign-in.

If it does not work in Zed

Zed does not connect
A green dot next to the server means it is active; anything else, check its state in the agent settings.
Zed says the organization does not let agents in
An owner or admin sets the organization's AI agents setting in the console, under Account, then Security. Off turns every agent away, and an owner or admin can also block one agent for one member there.
Zed cannot change anything
The organization is Read only, the default. An owner or admin can switch it to Read and change, and Zed can then make changes without signing in again. Deleting, sending to an audience, roles and money still ask you to approve each change.

Frequently Asked Questions

Which Zed plan do I need?

Zed's MCP page does not name a plan.

Can Zed change things in my BuildBase organization?

Only where the organization allows it: Read only is the default. Even then, deletes, member and role changes, sends and money moves need your approval in the chat, and secrets never reach Zed.

Can I connect Zed with an API key instead of signing in?

Yes, for a job with nobody to sign in: send one of your organization's API keys as the bearer. Add headers, with Authorization: Bearer <key>, to the server under context_servers; Zed then skips the sign-in. The key works in its own organization only, and the organization's AI agents setting still applies.

Where next