Skip to main content
Use this page after Client setup if you want an optional guided workflow for Centaur in agent-capable clients.

​
Overview

The public Centaur skill gives agent clients a guided way to use Centaur over MCP when it is already configured and fall back to REST when MCP is not available. It is a simple workflow layer on top of the connected Centaur server, not a replacement for the underlying REST and MCP reference.

​
Before you begin

Before you install the skill, make sure one of these is already true:
  • Centaur is configured in your client through MCP
  • CENTAUR_PARTNER_API_KEY is available for REST fallback
The skill does not run the OAuth flow or dynamic registration itself. It assumes your client has already connected to the Centaur MCP server.

​
Install

npx skills add https://github.com/centaur-io/centaur-partners-skill
Canonical repo:

​
How the skill works

The skill follows a standard decision path:
  1. Prefer MCP if Centaur is already configured in the current client.
  2. Otherwise look for CENTAUR_PARTNER_API_KEY.
  3. If the env var exists, use REST with x-api-key.
  4. Otherwise the user may paste a partner API key directly into the current chat for one-time use.
  5. If neither is available, stop and give setup instructions.

​
Supported surfaces

  • MCP endpoint: https://partners.centaur.io/mcp
  • MCP access to Centaur read families across events, messages, positions, discovery, and stats
  • REST fallback to matching endpoint families under https://partners.centaur.io/api/v1/*

​
Common reads

  • events
  • messages
  • positions
  • discovery
  • stats

​
Authentication and fallback

  • Preferred MCP: client-managed OAuth and Dynamic Client Registration against https://partners.centaur.io/mcp
  • MCP compatibility fallback: Authorization: Bearer <partner-api-key>
  • MCP last-resort fallback for custom connectors: https://partners.centaur.io/mcp?api_key=<partner-api-key>
  • REST: x-api-key: <partner-api-key>
For direct REST fallback, the skill expects: 
export CENTAUR_PARTNER_API_KEY='<partner-api-key>'
If the user does not want to set an environment variable yet, they may also paste a partner API key directly into the current chat for one-time REST use. That key should be treated as transient session input and should not be echoed back or persisted.

​
Notes

  • The connected Centaur MCP server remains the source of truth for the exact live tool inventory and resource URIs.
  • The skill should prefer an already-connected MCP server regardless of whether that client reached Centaur through OAuth or the temporary API-key compatibility path.
  • REST fallback uses the same scope-gated endpoint families described in the public API docs.

​
Supported clients

  • Claude
  • ChatGPT
  • Cursor
  • Codex
  • Claude Code
Set up Centaur in one of those clients first, then install the skill so the agent can choose MCP before REST fallback.

​
Repository contents

  • root SKILL.md
  • references/auth.md
  • references/mcp.md
  • references/rest.md
  • references/examples-curl.md
  • references/client-setup.md

​
Next steps

​
Resources

  • Public skill repo:
  • Machine discovery:
  • Install command:
Last modified on April 17, 2026