Skip to content
BuildBase
BuildBase in your AI tools

Use BuildBase in Cursor

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

Add to Cursor

Add BuildBase to Cursor

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

  1. In Cursor, add a remote MCP server: ~/.cursor/mcp.json or .cursor/mcp.json. Use the address https://api.console.buildbase.app/mcp, or the command or config below.
  2. Sign in. Cursor signs in with OAuth the first time the server is used, in your browser.
  3. On BuildBase's sign-in page, sign in as you do to the console, then approve the consent screen, which names Cursor and what it asks for.
  4. Ask Cursor something, such as "List my BuildBase organizations."
~/.cursor/mcp.jsonJSON
{
  "mcpServers": {
    "buildbase-console": {
      "url": "https://api.console.buildbase.app/mcp"
    }
  }
}

The plan it needs

Cursor's MCP page does not name a plan. On a team, an admin can hand out servers from the dashboard, and Enterprise can limit them to an allowlist.

How sign-in looks in Cursor

Cursor signs in with OAuth the first time the server is used, in your browser.

What is different in Cursor

  • Cursor asks before using an MCP tool by default. Tools follow the same run modes as terminal commands, so an allowlisted tool can run without asking.
  • 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 a headers object, with Authorization: Bearer <key>, next to url in mcp.json.
  • A one-click install link adds the server for you.
  • .cursor/mcp.json in a project, or ~/.cursor/mcp.json for every project.

If it does not work in Cursor

Cursor does not connect
Open the Output panel (Cmd+Shift+U, or Ctrl+Shift+U) and choose MCP Logs for start-up, tool calls and errors.
Cursor 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.
Cursor cannot change anything
The organization is Read only, the default. An owner or admin can switch it to Read and change, and Cursor 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 Cursor plan do I need?

Cursor's MCP page does not name a plan. On a team, an admin can hand out servers from the dashboard, and Enterprise can limit them to an allowlist.

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

Can I connect Cursor 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 a headers object, with Authorization: Bearer <key>, next to url in mcp.json. The key works in its own organization only, and the organization's AI agents setting still applies.

Where next