Skip to content
BuildBase
BuildBase in your AI tools

Use BuildBase in v0

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

Add BuildBase to v0

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

  1. In v0, add a remote MCP server: Prompt form + > MCPs, or the MCP Connections settings page. Use the address https://api.console.buildbase.app/mcp.
  2. Sign in. Choose OAuth when you add the server, then sign in when v0 asks.
  3. On BuildBase's sign-in page, sign in as you do to the console, then approve the consent screen, which names v0 and what it asks for.
  4. Ask v0 something, such as "List my BuildBase organizations."

The plan it needs

v0's MCP page does not name a plan, and says a remote MCP server may raise the cost of a message.

How sign-in looks in v0

Choose OAuth when you add the server, then sign in when v0 asks.

What is different in v0

  • v0 turns a whole server on or off; tool calls follow the chat's permission mode (Ask, Auto or Full).
  • 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 Bearer Token, or Custom Headers, as the authentication.
  • The tools work while v0 builds, in the chat. The app v0 generates cannot call them.

If it does not work in v0

v0 does not connect
v0 connects from its own servers, so the address must be public HTTPS.
v0 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.
v0 cannot change anything
The organization is Read only, the default. An owner or admin can switch it to Read and change, and v0 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 v0 plan do I need?

v0's MCP page does not name a plan, and says a remote MCP server may raise the cost of a message.

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

Can I connect v0 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 Bearer Token, or Custom Headers, as the authentication. The key works in its own organization only, and the organization's AI agents setting still applies.

Where next