Early access

Apply

Documentation
Developers/MCP/Connect Cursor

Connect Cursor

Add Supero to Cursor: put https://mcp.supero.dev/mcp in ~/.cursor/mcp.json, sign in in your browser, and build Supero apps from Cursor's agent.

  • Cursor
  • MCP
  • OAuth
  • mcp.json
  • remote MCP server

Overview

Cursor connects to Supero's MCP server at https://mcp.supero.dev/mcp and signs you in through your browser (OAuth). No API key is needed.

Tested

Checked end to end against Supero on 2026-11-13 with Cursor's documented sign-in: registration, browser sign-in, token refresh, and the tool list.

Add the server

Add Supero to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
json
{
  "mcpServers": {
    "supero": {
      "url": "https://mcp.supero.dev/mcp"
    }
  }
}
  1. 1

    Turn it on

    Open Cursor's settings, find the MCP section, and enable supero.

  2. 2

    Sign in

    Cursor opens your browser at Supero. Sign in, or create an account.

  3. 3

    Allow

    The approval page says "Supero hasn't verified this app", followed by the local address the tool uses (such as 127.0.0.1 or localhost). That is normal. Supero can't check a program on your computer, so it asks you to confirm you started the sign-in. Pick where it may work (access options). Click Allow.

  4. 4

    Use it

    Ask Cursor's agent to build an app; it calls the Supero tools.

Check the connection

Ask the assistant: "Use Supero and tell me who I am connected as." It calls build_whoami and answers with your workspace and access. Supero lists about 50 tools, with the build tools first.

Your first app

text
Build a booking app for a dog grooming salon: customers pick a groomer and a time slot and pay a deposit; staff see the day's appointments.

Use an API key instead (optional)

Only for CI pipelines, scripts, and machines without a browser. The tools are the same. Use https://api.supero.dev/mcp/v1/messages with the key in the X-API-Key header; Two addresses, one set of tools explains why there are two addresses, and Use an API key instead covers creating a key in the console (Build via MCP). A project key can read, change and delete records in every tenant of its project. Never commit a key.
json
{
  "mcpServers": {
    "supero": {
      "url": "https://api.supero.dev/mcp/v1/messages",
      "headers": { "X-API-Key": "ak_..." }
    }
  }
}

Troubleshooting

  • Use the URL exactly as https://mcp.supero.dev/mcp, with no trailing slash. Some clients compare it with the server's published resource and stop if they differ.
  • "Too many registrations" (HTTP 429). Each new sign-in registers the tool with Supero. One IP address may register 10 times an hour (an IPv6 /64 network 20 times), and there is an overall hourly limit. Wait, then try again. A sign-in that already works is not affected.
  • Signed in as the wrong account: remove the server, add it again, and use Switch account on the approval page.
  • To disconnect, use Disconnect at app.supero.dev/oauth/connections, then remove the server from the tool's config.
  • Changing your Supero password or email ends every assistant connection you signed in. Your projects and apps are not affected; sign in again from the tool.
  • Some Cursor versions pass only the first 40 tools to the model. All of Supero's build tools are in the first 40, so building works either way.