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

# Codex

> Add the Affixo MCP connector to Codex with two commands — register, then sign in.

Two commands. The first registers the connector; the second authenticates it.

```bash theme={null}
codex mcp add affixo --url https://go.affixo.dev/mcp
codex mcp login affixo
```

<Steps>
  <Step title="Register the connector">
    `codex mcp add` writes an entry into `~/.codex/config.toml`. Nothing can
    call it yet — it has no credentials.
  </Step>

  <Step title="Sign in">
    `codex mcp login affixo` opens Affixo in your browser. Sign in, then choose
    the **workspace** and the **access level**:

    * **Read only** — inspect campaigns, commissions, promoters and referrals.
    * **Read & write** — also create/update campaigns, set commission rules
      (including per-product rates), configure product commissions, and invite
      affiliates.

    You must be an **admin** of the workspace to authorize a connector.
  </Step>

  <Step title="Check it loaded">
    `codex mcp list` shows **affixo**. Ask: *"List my Affixo campaigns."*
  </Step>
</Steps>

## Adding it by hand

In `~/.codex/config.toml` (or `.codex/config.toml` to scope it to a trusted
project):

```toml theme={null}
[mcp_servers.affixo]
url = "https://go.affixo.dev/mcp"
auth = "oauth"
```

Then run `codex mcp login affixo` — the config alone doesn't authenticate.

<Note>
  Skipping the login step is the usual reason the tools appear but every call
  fails. Registering a connector and authorizing it are two separate things in
  Codex.
</Note>

Full tool catalogue and what each one can touch: [MCP Server](/mcp-server).
Installing *tracking* with Codex instead? See [Codex](/vibe/codex).