Skip to main content

​
Overview

Use this guide to register Centaur in Codex and verify that it can call list_events. That verification prompt is only a simple smoke test. Once connected, Codex 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 the Codex CLI or your local Codex configuration
Preferred server URL: 
https://partners.centaur.io/mcp

​
Set up Codex

  1. Add the server with the Codex CLI: 
    codex mcp add centaur-partners --url https://partners.centaur.io/mcp
  2. If you prefer a persistent config file, add the equivalent entry to ~/.codex/config.toml: 
    [mcp_servers.centaur-partners]
url = "https://partners.centaur.io/mcp"
  3. Let Codex dynamically register the MCP client if prompted.
  4. If Codex prompts for sign-in, continue in the browser and approve the Centaur access request.

​
Compatibility fallback

If your current Codex build cannot complete the OAuth flow yet, add the same server with a bearer API key header: 
codex mcp add centaur-partners --url https://partners.centaur.io/mcp \
  --header "Authorization: Bearer <partner-api-key>"
Or use persistent config: 
[mcp_servers.centaur-partners]
url = "https://partners.centaur.io/mcp"

[mcp_servers.centaur-partners.headers]
Authorization = "Bearer <partner-api-key>"

​
Verify the integration

After setup, confirm the server is registered: 
codex mcp list
Then verify with a prompt such as: 
Use the centaur-partners MCP server to call list_events with limit 5.
After that succeeds, the MCP setup is ready for the wider supported Centaur reads.

​
Install the Centaur skill

Now that Codex 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 codex mcp list does not show centaur-partners, rerun the codex mcp add command and confirm the URL is unchanged.
  • If the browser sign-in flow does not appear or does not complete, use the compatibility fallback header configuration.
  • If you manage MCP servers through config.toml, restart Codex after saving the file.
  • Some OpenAI API-side MCP integrations may still require your application to supply an access token directly. This guide is for the interactive Codex client flow.

​
Next steps

Last modified on April 17, 2026