Connecting Cursor

RequirementsCopy Anchor Link

• Cursor 0.46 or newer (MCP support GA).
• A Zuse Bifrost account. Cursor signs you in; a personal access token is only needed when you want a connection narrower than your own reach.

The server address is written as https://mcp.example.test below; use the one your administrator shares.

ConfigCopy Anchor Link

Cursor's MCP configuration lives at ~/.cursor/mcp.json on macOS / Linux and %APPDATA%/Cursor/mcp.json on Windows.

{
  "mcpServers": {
    "zusegenius": {
      "url": "https://mcp.example.test"
    }
  }
}

Using a personal access token insteadCopy Anchor Link

Mint a token under Account Settings → API Tokens with the abilities you want Cursor to exercise and send it as a header; Cursor then skips the sign-in:

{
  "mcpServers": {
    "zusegenius": {
      "url": "https://mcp.example.test",
      "headers": {
        "Authorization": "Bearer zg_live_YOUR_TOKEN"
      }
    }
  }
}

Project-scoped versus user-scopedCopy Anchor Link

Cursor also supports per-workspace .cursor/mcp.json. If you want the Zuse Bifrost integration active only inside a specific repository, put the config there instead of the global location, with a token scoped to that repository's project.

TroubleshootingCopy Anchor Link

• Stuck on "Needs login": the URL must be exactly the server's address; finish the browser sign-in and return to Cursor, which retries on its own.
• Tool list empty: check Cursor's "MCP" panel in the settings drawer for connection errors.
• A refusal on a call with a personal access token: the token lacks that tool's ability. The response names it in error.context.required_ability.
• Not found on specific tools: the token's team or project scope does not include the entity you referenced; see the tools reference.