Skip to main content

​
Overview

Use this guide to register Centaur as a remote MCP server in Cursor and verify that it can call list_events. That verification prompt is only a simple smoke test. Once connected, Cursor can use the broader Centaur surface across events, messages, positions, discovery, and stats.

​
Before you begin

Before you begin, make sure you have:
  • A Centaur account that already has partner access enabled
  • Access to your local Cursor MCP configuration
Preferred server URL: 
https://partners.centaur.io/mcp

​
Set up Cursor

  1. Create ~/.cursor/mcp.json and register Centaur as a remote MCP server: 
    {
  "mcpServers": {
    "centaur-partners": {
      "url": "https://partners.centaur.io/mcp"
    }
  }
}
  2. Restart Cursor.
  3. Let Cursor dynamically register the MCP client if prompted.
  4. If Cursor prompts for sign-in, continue in the browser and approve the Centaur access request.

​
Compatibility fallback

If your current Cursor build cannot complete the OAuth flow yet:
  1. Export your Centaur partner API key: 
    export CENTAUR_PARTNER_API_KEY='<partner-api-key>'
  2. Add the auth header to the same ~/.cursor/mcp.json entry: 
    {
  "mcpServers": {
    "centaur-partners": {
      "url": "https://partners.centaur.io/mcp",
      "headers": {
        "Authorization": "Bearer ${env:CENTAUR_PARTNER_API_KEY}"
      }
    }
  }
}

​
Verify the integration

After setup, open Cursor and ask: 
Use centaur-partners to call list_events with limit 5.
Confirm centaur-partners appears in Cursor MCP settings and returns results from list_events. After that succeeds, the MCP setup is ready for the wider supported Centaur reads.

​
Install the Centaur skill

Now that Cursor is connected, install the Public skill to get a guided Centaur workflow in your client. 
npx skills add https://github.com/centaur-io/centaur-partners-skill
For setup details and fallback behavior, see the Public skill page.

​
Troubleshooting

  • If centaur-partners does not appear in Cursor, restart the app after updating mcp.json.
  • If the OAuth browser flow does not appear or does not complete, use the compatibility fallback header configuration.
  • If the server appears but fails to authenticate in fallback mode, confirm the environment variable is available in the shell session that launched Cursor.

​
Next steps

Last modified on April 17, 2026