Skip to main content

Connect Cursor

OAuth browser sign-in​

Sign in with your Reconstruct account in the browser. You do not need to create a personal token on the Platform. See MCP OAuth setup for the shared connection settings.

Add the reconstruct entry to ~/.cursor/mcp.json, preserving other servers:

{
  "mcpServers": {
    "Reconstruct": {
      "url": "https://reconstruct.dev/mcp",
      "auth": {
        "CLIENT_ID": "reconstruct-mcp",
        "scopes": ["openid", "aud-mcp"]
      }
    }
  }
}

Enable the server and follow the browser sign-in. Desktop uses http://localhost:8787/callback; Cursor's web/agent callback is https://www.cursor.com/agents/mcp/oauth/callback. Both are registered. Remove any manually configured Authorization header when choosing OAuth. See Cursor static OAuth.

Refresh an existing connection​

The discovered issuer must be https://reconstruct.dev/sso/realms/reconstruct. The browser should open https://reconstruct.dev/sso/realms/reconstruct/protocol/openid-connect/auth. A URL ending in /authorize at the site root indicates stale or missing discovery metadata.

Disable and enable the Reconstruct server, then repeat sign-in. Restart Cursor if it keeps the old metadata; recreate only this server entry if necessary. Check Output → MCP Logs for connection errors. Keep the callback settings above and leave the client secret empty.

Personal access token​

Copy your MCP access token from your Reconstruct Platform account settings. See Personal access token for the connection requirements. Set CR_RECONSTRUCT_MCP_TOKEN in the environment that launches Cursor.

Create ~/.cursor/mcp.json:

{
  "mcpServers": {
    "Reconstruct": {
      "url": "https://reconstruct.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${env:CR_RECONSTRUCT_MCP_TOKEN}"
      }
    }
  }
}

Enable the server in Cursor's MCP settings, restart the agent if its tool list was already loaded, and ask it to call list_products. See the official Cursor MCP documentation.

Next, try the prompt examples.