Which transport do I pick in Bolt?

HTTP, the standard one. BuildBase's server speaks Streamable HTTP, not SSE.

Can I turn BuildBase on for one project only?

No. Bolt's docs say the tools you enable apply to all your projects. Disconnect the connector when you do not want it.

Can my published Bolt app call these tools?

No. The connection serves Bolt while it builds. Your app talks to BuildBase through the SDK with its own keys.

Use BuildBase in Bolt

Add BuildBase's MCP server to Bolt as a custom connector with MCP OAuth, and let Bolt read and set up your organization while it builds.

This page is part of BuildBase in your AI tools: it connects Bolt to BuildBase's own MCP server so that, while Bolt builds your app, it can read and set up your BuildBase organization. Bolt signs in as you and never sees your organization's secrets.

Note

Want your own app to be agent-ready? See Connect an agent to your app, in Agent-ready apps.

What it is for

Connected to BuildBase, Bolt can look things up and set your organization up while it writes the code:

get_env_template gives the environment variables a Vite app needs, with your organization's id filled in and every secret left for you.
search_docs and fetch_doc read the BuildBase docs, so Bolt uses the SDK the way it is documented.
With your approval of the scope, it can create a feature flag or a form, or plan a blueprint for the organization the app needs.

The app itself uses @buildbase/sdk with its own keys, as the Bolt guides set it up.

What you need

A Bolt account. Bolt's docs name no plan for custom MCP servers.
A BuildBase console account, and an organization whose AI agents setting is not Off (choose what agents may do).

Add the connector

In the chat box, choose + > Connectors > Manage connectors.
Choose Custom MCP server and fill in:
- Name: BuildBase
- URL:
```
https://api.console.buildbase.app/mcp
```
- Transport: HTTP
- Authentication: MCP OAuth
Choose Connect.

Bolt opens BuildBase's sign-in page. Sign in with your console account and your usual second step, then approve Bolt on the consent screen. It asks for console:read and console:write to start; an export or a delete asks again for just that scope (what an agent asks for).

What you see when you connect

Once you have signed in, BuildBase shows the consent screen in your browser. It names the tool, lists the scopes it asks for and the server the access is for, and changes nothing until you choose Allow access. Here it is for a tool that registered itself:

BuildBase's consent screen for a tool that registered itself, here Example Agent: a warning that the app gave itself its name and nobody has checked it, what it may do as you, console:read and offline_access, the access to use at https://api.console.buildbase.app/mcp, and Allow access and Deny ringed

Use it

Ask, for example:

"Add BuildBase sign-in to this Vite app. Get the environment variables for my Acme organization from BuildBase."
"Read the BuildBase docs on credits and show the user's balance in the header."
"Plan a BuildBase blueprint with the roles this app needs, and show me the plan."

What differs in Bolt

Tools apply to every project. Bolt has no per-project switch for a connector's tools, so BuildBase's tools are there in each project while it is connected.
Authentication options. Bolt also offers an API key and no auth. With an organization API key Bolt acts as that key, not as you; keep MCP OAuth.
Approvals of a change. When BuildBase needs your approval for a change, the agent states it and confirms it with a one-time code unless Bolt can ask you itself (what stays with you).
Secrets stay out of the chat. Put your sign-in client's secret in the project's environment yourself, never in the prompt.

If something goes wrong

What you see	Why	What to do
The connector shows as offline	The connection dropped or the sign-in ended	Open ⋯ > Edit and choose Refresh connection
It never connects	Transport is SSE	Edit it to HTTP
Bolt says the organization does not let agents in	Its AI agents setting is Off, or your agent is blocked	An owner or admin changes it under Security, AI agents
Every change is refused	The organization is Read only, or you did not grant `console:write`	An owner or admin sets Read and change; approve `console:write`

To disconnect, remove the connector in Bolt and disconnect the agent in BuildBase.

BuildBase in your AI tools: the server, its tools, and what stays with you.
Use BuildBase in Lovable and Use BuildBase in Replit.
Add BuildBase to Bolt's knowledge or skills and add paid plans to a Bolt app: the paste-prompt guides.
Bolt's own guide: connect MCP.

Frequently asked questions

Which transport do I pick in Bolt?: HTTP, the standard one. BuildBase's server speaks Streamable HTTP, not SSE.
Can I turn BuildBase on for one project only?: No. Bolt's docs say the tools you enable apply to all your projects. Disconnect the connector when you do not want it.
Can my published Bolt app call these tools?: No. The connection serves Bolt while it builds. Your app talks to BuildBase through the SDK with its own keys.