Skip to content
BuildBase
Agent-ready apps

Let your users connect Cursor to your app

Agent-ready apps: make the app you build with the SDK ready for Cursor. Your users add your app's MCP server to Cursor, sign in on your hosted page and approve it, and Cursor acts as them, never as more.

How your users add your app to Cursor

Give your users your app's MCP address. npx buildbase agent install --url <your MCP address> prints the setup for each AI tool, Cursor included, with your address filled in.

  1. In Cursor, your user adds a remote MCP server: ~/.cursor/mcp.json or .cursor/mcp.json. They use your app's MCP address, https://app.example.com/api/mcp in these examples, 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. Your hosted sign-in page opens. Your user signs in and approves the consent screen, which names Cursor and what it asks for.
  4. Cursor can now use your tools, as that user and with that user's permissions.
~/.cursor/mcp.jsonJSON
{
  "mcpServers": {
    "acme": {
      "url": "https://app.example.com/api/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 runs on your user's own computer, so it reaches any address that computer can, including a development server while you test.
  • Your server's built-in tools are read-only until you allow changes. 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.
  • 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 cannot register or sign in
Turn on Let agents register themselves, with a base client, in the console under Authentication, then Agent readiness. Cursor registers its own client the first time it connects.
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.
Check your server the way Cursor will
Run npx buildbase agent doctor --url <your MCP address>. It walks the first contact a client makes (the sign-in challenge, the metadata, redirects, a stable tool list) and exits 1 when a check fails.

Frequently Asked Questions

Which Cursor plan do your users 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.

Does my MCP server need to be public for Cursor?

No. Cursor runs on your user's computer, so it reaches what that computer reaches. Your users still need an address they can open, and production should be public HTTPS.

Can Cursor change data in my app?

Only through tools you allow, and only as the user who connected it. The built-in tools are read-only by default, and a tool that needs extra scopes is hidden until the user grants them.

Where next