Skip to main content
Use this page to understand when MCP is the right integration path for Centaur and what the MCP surface exposes. For most external users, start with Client setup.

​
Overview

Use MCP when you want an agent or IDE client to call Centaur tools directly instead of working through raw REST requests.

​
When to use MCP

Choose MCP when:
  • your users work in Claude, ChatGPT, Cursor, Codex, or similar agent-capable clients
  • you want native tool calling instead of hand-crafted HTTP requests
  • you want agent workflows to stay aligned with the public Centaur skill repo
Choose REST when:
  • you need a conventional backend integration
  • you want complete control over HTTP calls and retries
  • your client does not support MCP

​
Endpoint

https://partners.centaur.io/mcp

​
Authentication

Preferred path:
  • Add the plain MCP URL above in a supported client
  • Let the client dynamically register itself when it needs a new OAuth client
  • Let the client complete the OAuth sign-in and consent flow
  • Reuse the issued access token for later MCP calls
Compatibility fallback during migration:
  • Authorization: Bearer <partner-api-key> when the client supports custom headers
  • https://partners.centaur.io/mcp?api_key=<partner-api-key> only when the client cannot send headers at all
Some OpenAI API-side MCP integrations may still require the calling application to supply an OAuth access token directly. This page covers interactive client flows first.

​
What Centaur exposes over MCP

Centaur exposes read-only partner data capability families over MCP:
  • events
  • messages
  • positions
  • discovery
  • stats

​
Scope families

  • events.read
  • messages.read
  • positions.read
  • directory.read
  • stats.read
The exact live tool and resource inventory is discoverable from the MCP server itself and may grow over time without changing the onboarding model on this page. Today, discovery and aggregate stats are separate read families, so agents can use list_traders and list_assets to resolve IDs before calling detail stats.

​
Compatibility example request

curl -s 'https://partners.centaur.io/mcp' \
  -H 'accept: application/json, text/event-stream' \
  -H 'content-type: application/json' \
  -H 'authorization: Bearer <partner-api-key>' \
  -d '{"jsonrpc":"2.0","id":"tool-call-1","method":"tools/call","params":{"name":"list_messages","arguments":{"limit":10}}}'
The connected client can call any supported Centaur tool after setup, not only the example shown above.

​
Get started

Last modified on April 20, 2026