Prerequisites
Before you begin, make sure you have:- A Centaur account that already has partner access enabled, or a valid partner API key if you expect to use the compatibility path
- One of the supported clients: Claude, ChatGPT, Cursor, Codex, or Claude Code
- Access to update connector settings or local MCP configuration for your client
Preferred setup
For all supported clients, start with the plain MCP server URL: If the client supports MCP OAuth, it should then:- discover the protected-resource and authorization-server metadata
- dynamically register itself if it needs a new OAuth client
- open a Centaur sign-in flow in the browser
- ask you to approve the requested MCP scopes
- reconnect with the issued bearer token automatically
Compatibility fallback
If your current client build cannot complete OAuth yet:- use
Authorization: Bearer <partner-api-key>when the client supports custom headers - use only when the client cannot send MCP auth headers at all
list_traders and list_assets for discovery before detail stats calls when IDs are not known yet.
Choose your client
Claude
Use the hosted Claude connector flow with the plain MCP URL and browser-based OAuth.
ChatGPT
Use the hosted ChatGPT connector flow when your workspace supports custom connectors or GPT actions.
Cursor
Use the Cursor guide when you want Centaur available inside a local IDE MCP setup.
Codex
Use the Codex guide when you want to register Centaur through the Codex CLI or config file.
Claude Code
Use the Claude Code guide when you want a local Anthropic MCP configuration.
Next steps
- MCP overview
- Public skill for an optional guided workflow after setup
- REST overview if MCP is not the right fit