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 the partner feed, events, messages, generated summaries, positions, discovery, and stats.

​
Before you begin

Before you begin, make sure you have:
  • A Centaur account that is active with a verified email
  • Access to your local Cursor MCP configuration
Preferred server URL:

​
Set up Cursor

  1. Create ~/.cursor/mcp.json and register Centaur as a remote MCP server:
  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.

​
Verify the integration

After setup, open Cursor and ask:
Confirm centaur 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.
For setup details, see the Public skill page.

​
Troubleshooting

  • If centaur does not appear in Cursor, restart the app after updating mcp.json.
  • If the OAuth browser flow does not appear or does not complete, remove and recreate the server entry so Cursor can retry registration.

​
Next steps

Last modified on August 6, 2026