Start
Connect your assistant
AffiliateOS is a remote connector: one URL, added from a settings screen, authorized with a sign-in popup. You do not need a terminal, a code editor, or an API key to set it up.
The only thing you need to copy
Every app below takes the same address. Name the connector affiliateos when it asks for a name.
https://api.affiliateos.dev/mcpClaude
In the Claude desktop app or claude.ai — no terminal, no API key.
- 1Open Settings, then Connectors.
- 2Choose "Add custom connector".
- 3Name it affiliateos and paste the URL below.
- 4Click Connect and sign in when the popup appears. That is it.
Custom connectors are available on Claude’s paid plans.
ChatGPT
Same URL, same sign-in popup, from ChatGPT’s connector settings.
- 1Open Settings, then Connectors (or Apps & Connectors).
- 2Add a custom connector / remote MCP server.
- 3Paste the URL below and save.
- 4Authorize AffiliateOS in the sign-in popup.
Custom connectors depend on your ChatGPT plan; on some plans they sit behind developer mode in settings.
Other apps
Codex, Cursor, VS Code, n8n and anything else that speaks MCP over HTTP take the same URL.
- 1Find the app’s MCP servers or Connectors settings.
- 2Add a remote / HTTP / streamable-HTTP server.
- 3Paste the URL below and authorize when prompted.
- 4If it only accepts a config file, paste the JSON snippet instead of the URL.
Clients that cannot do OAuth can send a dashboard-issued API key as a Bearer header instead.
Apps that want a config file
Some MCP clients have no settings form and read a JSON file instead. Add this block to the client’s MCP configuration:
{
"mcpServers": {
"affiliateos": {
"type": "http",
"url": "https://api.affiliateos.dev/mcp"
}
}
}From the terminal
Entirely optional, and equivalent to the settings-screen flow above.
claude mcp add --transport http affiliateos https://api.affiliateos.dev/mcpIf something goes wrong
| What you see | What it means |
|---|---|
| No "Add custom connector" button | Custom connectors are a paid-plan feature in Claude, and are plan-gated in ChatGPT too. Check your plan, or use an API key with the REST API instead. |
| The sign-in popup never opens | Popups are blocked, or the app cached a failed attempt. Allow popups for the app, remove the connector, and add it again. |
| Connected, but the assistant finds no programs | The connector is working; you have not linked a network yet. Add your first one in the dashboard — see network guides. |
| The client cannot do OAuth | Issue an API key in Developers and send it as Authorization: Bearer aff_live_…. |
Next
Once the connector is live, the quickstart walks through connecting a network and running your first discover-mint-measure loop. The MCP reference lists every tool the assistant gains.