> ## 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.

# Claude Code

> Add the Affixo MCP connector to Claude Code with one command.

One command, from your project root:

```bash theme={null}
claude mcp add --transport http affixo https://go.affixo.dev/mcp
```

<Steps>
  <Step title="Run the command">
    It registers a server named `affixo`. Add `--scope user` if you want it
    available in every project rather than just this one.
  </Step>

  <Step title="Sign in">
    Run `/mcp` in Claude Code, pick **affixo**, and authenticate. Affixo opens
    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">
    `/mcp` should show **affixo** connected. Ask: *"List my Affixo campaigns."*
  </Step>
</Steps>

## Adding it by hand

In `.mcp.json` at the project root (checked in, so your team gets it too):

```json theme={null}
{
  "mcpServers": {
    "affixo": {
      "type": "http",
      "url": "https://go.affixo.dev/mcp"
    }
  }
}
```

<Note>
  No API key at any point. If you find instructions telling you to paste an
  `sa_live_` key into `.mcp.json`, they're out of date — the connector
  authenticates in the browser and issues a workspace-scoped token behind the
  scenes.
</Note>

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