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

# Codex

> Set up Centaur in Codex through the Codex CLI or config file with OAuth-first auth.

## 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 the partner feed, events, messages, generated summaries, positions, discovery, and stats.

## Before you begin

Before you begin, make sure you have:

* A Centaur account that is active with a verified email
* Access to the Codex CLI or your local Codex configuration

Preferred server URL:

```text theme={null}
https://partners.centaur.io/mcp
```

## Set up Codex

1. Add the server with the Codex CLI:

   ```bash theme={null}
   codex mcp add centaur --url https://partners.centaur.io/mcp
   ```

2. If you prefer a persistent config file, add the equivalent entry to `~/.codex/config.toml`:

   ```toml theme={null}
   [mcp_servers.centaur]
   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.

## Verify the integration

After setup, confirm the server is registered:

```bash theme={null}
codex mcp list
```

Then verify with a prompt such as:

```text theme={null}
Use Centaur 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](/docs/guides/mcp-agents/public-skill) to get a guided Centaur workflow in your client.

```bash theme={null}
npx skills add https://github.com/centaur-io/centaur-partners-skill
```

For setup details, see the [Public skill page](/docs/guides/mcp-agents/public-skill).

## Troubleshooting

* If `codex mcp list` does not show `centaur`, 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, remove and recreate the server entry so Codex can retry OAuth.
* 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

* [Client setup](/docs/guides/mcp-agents/client-setup)
* [MCP overview](/docs/guides/mcp-agents/overview)