Skip to main content

​
Overview

Use this guide to register Centaur in Claude Code and verify that it can call list_events. That verification prompt is only a simple smoke test. Once connected, Claude Code 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 the Claude Code CLI on your machine
Preferred server URL: 
https://partners.centaur.io/mcp

​
Set up Claude Code

  1. Register Centaur with a bearer auth header: 
    claude mcp add --transport http centaur-partners https://partners.centaur.io/mcp
  2. If Claude Code prompts for sign-in, continue in the browser and approve the Centaur access request.

​
Compatibility fallback

If your Claude Code build cannot complete the OAuth flow yet, register Centaur with a bearer API key header: 
claude mcp add --transport http centaur-partners https://partners.centaur.io/mcp \
  --header "Authorization: Bearer <partner-api-key>"

​
Verify the integration

After setup, confirm the server is registered: 
claude mcp list
Then verify inside Claude Code with a request such as: 
Call list_events with limit 5 and summarize the response.
After that succeeds, the MCP setup is ready for the wider supported Centaur reads.

​
Install the Centaur skill

Now that Claude Code 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 claude mcp list does not show centaur-partners, rerun the registration command and confirm the MCP URL is unchanged.
  • If the browser sign-in flow does not appear or does not complete, use the compatibility fallback header configuration.

​
Next steps

Last modified on April 20, 2026