Overview
Use this guide to register Centaur as a remote MCP server in Cursor and verify that it can calllist_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
- The public Cursor OAuth client ID supplied by Centaur for the environment you are connecting to
Set up Cursor
-
Add the following entry to
~/.cursor/mcp.json. Preserve your other servers and replace<CENTAUR_CURSOR_CLIENT_ID>with the public client ID: - Restart Cursor.
- Connect to Centaur in Cursor MCP settings. The client ID identifies Cursor; it is public and does not replace your sign-in. No client secret or API key is needed.
- 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: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.Troubleshooting
- If
centaurdoes not appear in Cursor, restart the app after updatingmcp.json. - If the OAuth browser flow does not appear or does not complete, check the client ID and reconnect. A client ID from another environment will not work.