Skip to content
BuildBase
BuildBase in your AI tools

Use BuildBase in VS Code

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

Add to VS Code

Add BuildBase to VS Code

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

  1. In VS Code, add a remote MCP server: code --add-mcp, or .vscode/mcp.json. Use the address https://api.console.buildbase.app/mcp, or the command or config below.
  2. Sign in. The first time it connects, VS Code opens a browser to sign in. It registers its own client; the account then appears in the Accounts menu, where you can sign out.
  3. On BuildBase's sign-in page, sign in as you do to the console, then approve the consent screen, which names VS Code and what it asks for.
  4. Ask VS Code something, such as "List my BuildBase organizations."
terminalBash
code --add-mcp '{"name":"buildbase-console","type":"http","url":"https://api.console.buildbase.app/mcp"}'
.vscode/mcp.jsonJSON
{
  "servers": {
    "buildbase-console": {
      "type": "http",
      "url": "https://api.console.buildbase.app/mcp"
    }
  }
}

The plan it needs

On Copilot Business and Enterprise, the organization's "MCP servers in Copilot" policy must be on, and it is off by default. GitHub says the policy applies to those two plans only.

How sign-in looks in VS Code

The first time it connects, VS Code opens a browser to sign in. It registers its own client; the account then appears in the Accounts menu, where you can sign out.

What is different in VS Code

  • Choose which tools the agent may use from Configure Tools in the chat input, and approve each call when VS Code asks.
  • 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 to the server in mcp.json; an inputs entry with password: true asks for the key once instead of storing it in the file.
  • VS Code uses servers, not mcpServers, and type: "http".
  • A one-click install link opens a page that shows the server before you install it.

If it does not work in VS Code

VS Code does not connect
MCP: List Servers starts, stops and restarts a server, and Show Output shows its log. Run MCP: Reset Cached Tools after the tool list changes.
VS Code 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.
VS Code cannot change anything
The organization is Read only, the default. An owner or admin can switch it to Read and change, and VS Code 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 VS Code plan do I need?

On Copilot Business and Enterprise, the organization's "MCP servers in Copilot" policy must be on, and it is off by default. GitHub says the policy applies to those two plans only.

Can VS Code 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 VS Code.

Can I connect VS Code 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 to the server in mcp.json; an inputs entry with password: true asks for the key once instead of storing it in the file. The key works in its own organization only, and the organization's AI agents setting still applies.

Where next