> ## Documentation Index
> Fetch the complete documentation index at: https://docs.centaur.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Client Setup

> Choose a supported client and follow the matching setup guide for the Centaur MCP server.

export const mcpUrl = 'https://mcp.centaur.io/mcp';

Use this page to choose the right setup guide for your client and connect it to the Centaur MCP server.

## Prerequisites

Before you begin, make sure you have:

* A Centaur account that is active with a verified email
* 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

Official Claude and ChatGPT directory installs use this OAuth setup path.

Claude, ChatGPT, Codex, and Claude Code start with the MCP server URL:

<code>
  {mcpUrl}
</code>

If the client supports MCP OAuth, it should then:

1. discover the protected-resource and authorization-server metadata
2. identify itself through client metadata or the client-specific setup guide
3. open a Centaur sign-in flow in the browser
4. ask you to approve the requested MCP scopes
5. reconnect with the issued bearer token automatically

Cursor also needs the public client ID supplied by Centaur. Follow the [Cursor setup guide](/guides/mcp-agents/clients/cursor) before connecting.

Interactive ChatGPT and Codex clients should use the flow above. Some OpenAI API-side MCP integrations may still require your application to obtain and supply an access token directly.

After setup, the client can call tool families covered by its granted scopes, including the partner feed, events, messages, generated summaries, positions, discovery, and stats. Use `list_trader_directory` and `list_assets` for discovery before detail stats calls when IDs are not known yet. This workflow requires both `directory.read` for discovery and `stats.read` for stats. A call without its required scope returns a missing-permission error.

## Choose your client

* [Claude](/guides/mcp-agents/clients/claude)
* [ChatGPT](/guides/mcp-agents/clients/chatgpt)
* [Cursor](/guides/mcp-agents/clients/cursor)
* [Codex](/guides/mcp-agents/clients/codex)
* [Claude Code](/guides/mcp-agents/clients/claude-code)

<Columns cols={2}>
  <Card title="Claude" href="/guides/mcp-agents/clients/claude" icon="bot" cta="Open guide" arrow>
    Use the hosted Claude connector flow with the plain MCP URL and browser-based OAuth.
  </Card>

  <Card title="ChatGPT" href="/guides/mcp-agents/clients/chatgpt" icon="sparkles" cta="Open guide" arrow>
    Use the hosted ChatGPT OAuth flow when your workspace supports custom MCP plugins.
  </Card>

  <Card title="Cursor" href="/guides/mcp-agents/clients/cursor" icon="monitor" cta="Open guide" arrow>
    Use the Cursor guide when you want Centaur available inside a local IDE MCP setup.
  </Card>

  <Card title="Codex" href="/guides/mcp-agents/clients/codex" icon="terminal" cta="Open guide" arrow>
    Use the Codex guide when you want to register Centaur through the Codex CLI or config file.
  </Card>

  <Card title="Claude Code" href="/guides/mcp-agents/clients/claude-code" icon="square-terminal" cta="Open guide" arrow>
    Use the Claude Code guide when you want a local Anthropic MCP configuration.
  </Card>
</Columns>

## Next steps

* [MCP overview](/guides/mcp-agents/overview)
* [Public skill](/guides/mcp-agents/public-skill) for an optional guided workflow after setup
* [REST overview](/guides/rest/overview) if MCP is not the right fit