Use BuildBase in Cursor

This page is part of BuildBase in your AI tools: it connects Cursor to BuildBase's own MCP server so you can manage your BuildBase organization from Cursor's agent. Cursor signs in as you and never sees your organization's secrets.

What you need

• Cursor.
• A BuildBase console account, whichever way you sign in to the console.
• An organization whose AI agents setting is not Off (choose what agents may do). Agents can read by default.

Add the server

In one click: use the Cursor button under connect in one click, or open this link:

cursor://anysphere.cursor-deeplink/mcp/install?name=buildbase-console&config=eyJ1cmwiOiJodHRwczovL2FwaS5jb25zb2xlLmJ1aWxkYmFzZS5hcHAvbWNwIn0%3D

By hand: add the entry to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "buildbase-console": {
      "url": "https://api.console.buildbase.app/mcp"
    }
  }
}

The link carries exactly this entry, base64-encoded.

Sign in

Cursor registers itself with BuildBase as a public client, then opens BuildBase's sign-in page in your browser.

1. Sign in with your console account and your usual second step.
2. Read the consent screen: it names the client and the scopes it asks for, console:read and console:write to start. Approve it.

When a task needs more, such as an export or a delete, Cursor is told which scope is missing (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:

Use it while you build

Ask Cursor's agent, for example:

• "Which environment variables does this Next.js app need for Acme? Fill .env.example, secrets left blank."
• "Create a feature flag new-editor, off, in staging, and gate the new editor on it here."
• "Write a blueprint for our roles and forms and show me the plan."

More, with what each one asks you to approve: example prompts.

What differs in Cursor

• The only tool with a one-click link besides VS Code. The link adds the server; sign-in still happens in your browser.
• Approval before each tool, by default. Keep it for console_write, console_destructive_change, create_org and blueprint_apply.
• Approvals of a change. Where Cursor can ask you a question itself, the change BuildBase wants to make is shown to you and nothing happens unless you approve it. Otherwise it states the change and confirms it with a one-time code (what stays with you).
• API keys. For a job with nobody to sign in, an entry can send a header instead, such as "headers": { "Authorization": "Bearer ${env:BUILDBASE_API_KEY}" } (connect with an API key).

If something goes wrong

To disconnect, remove the entry from mcp.json and disconnect the agent in BuildBase, which ends its session at once.

Related

• BuildBase in your AI tools: the server, its tools, and what stays with you.
• Use BuildBase in VS Code and Use BuildBase in Claude Code.
• Let your users connect Cursor to your app: the same client in Agent-ready apps.
• Cursor's own guide: MCP in Cursor.