Skip to main content

​
Overview

Use this guide to connect Centaur to Claude through a custom connector and verify that Claude can call list_events. That verification prompt is only a simple smoke test. Once connected, Claude 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 Claude connector settings
Preferred server URL:

​
Set up Claude

  1. Open Claude and go to Settings > Connectors.
  2. Click Add custom connector.
  3. Name it Centaur Partners.
  4. Paste into Remote MCP Server URL.
  5. Save the connector.
  6. If Claude prompts for sign-in, continue in the browser and approve the Centaur access request.
  7. Enable the connector in your chat.
Claude custom connectors should use the plain Centaur MCP URL first. Claude can dynamically register the connector during the OAuth flow when the workspace supports that path. If your workspace is configured for Anthropic-held or manually provisioned client credentials instead, use Claude Advanced settings as the fallback path rather than the default one.

​
Compatibility fallback

If your Claude workspace cannot complete the OAuth flow yet, recreate the connector with:

​
Verify the integration

After setup, open a chat and ask: 
Use Centaur Partners to call list_events with limit 5 and summarize the response.
Confirm Claude can discover the connector and return results from list_events. After that succeeds, the connector is ready for the wider supported Centaur reads.

​
Install the Centaur skill

Now that Claude 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 cannot discover the connector, reopen the chat after enabling it.
  • If Claude says the connector cannot authenticate, remove and recreate the connector with the plain MCP URL so it can retry Dynamic Client Registration.
  • If your workspace uses Anthropic-held or manually provisioned client credentials, verify that those credentials match the current environment.
  • If Claude cannot complete the browser sign-in flow after that, use the compatibility fallback URL above.

​
Next steps

Last modified on April 20, 2026