Skip to content
BuildBase
BuildBase in your AI tools

Use BuildBase in Bolt

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

Add BuildBase to Bolt

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

  1. In Bolt, add a remote MCP server: + > Connectors > Manage connectors > Custom MCP server. Use the address https://api.console.buildbase.app/mcp.
  2. Sign in. Choose MCP OAuth as the authentication, then Connect; the server shows Connected.
  3. On BuildBase's sign-in page, sign in as you do to the console, then approve the consent screen, which names Bolt and what it asks for.
  4. Ask Bolt something, such as "List my BuildBase organizations."

The plan it needs

Bolt's MCP page does not name a plan.

How sign-in looks in Bolt

Choose MCP OAuth as the authentication, then Connect; the server shows Connected.

What is different in Bolt

  • Open the connector, then the three dots > Edit, and deselect the tools Bolt should not use. It applies to every project.
  • 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. Choose API key as the authentication.

If it does not work in Bolt

Bolt needs to sign in again
Open the connector, choose Edit, then Refresh connection.
Bolt does not connect
A server shown offline: Edit > Refresh connection. Choose HTTP as the transport.
Bolt 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.
Bolt cannot change anything
The organization is Read only, the default. An owner or admin can switch it to Read and change, and Bolt 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 Bolt plan do I need?

Bolt's MCP page does not name a plan.

Can Bolt 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 Bolt.

Can I connect Bolt 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. Choose API key as the authentication. The key works in its own organization only, and the organization's AI agents setting still applies.

Where next