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.

connector URL

https://api.affiliateos.dev/mcp

Pasting this URL never exposes anything. It points at the AffiliateOS server; your account is only linked after you sign in through the popup, and you can disconnect it at any time from Developers → OAuth connections in the dashboard.

Claude

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:

json

{
  "mcpServers": {
    "affiliateos": {
      "type": "http",
      "url": "https://api.affiliateos.dev/mcp"
    }
  }
}

From the terminal

Entirely optional, and equivalent to the settings-screen flow above.

shell

claude mcp add --transport http affiliateos https://api.affiliateos.dev/mcp

If 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_…`.

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.

Common questions

How do I connect Claude to an affiliate network?

Add AffiliateOS as a custom connector in Claude's settings, paste the URL https://api.affiliateos.dev/mcp, and sign in through the popup. Claude then has tools to search affiliate programs, mint tracked links and read earnings. The networks themselves — Awin, Impact, CJ, Rakuten, Amazon — are connected once using API credentials from your own accounts. You can ask Claude to connect one: it hands you a short-lived link to the AffiliateOS dashboard, you enter the credential there, and it is told whether that worked. Agents can never submit or read network credentials themselves.

Is there an MCP server for affiliate marketing?

Yes. AffiliateOS is a streamable-HTTP MCP server at https://api.affiliateos.dev/mcp exposing 21 tools across program discovery, link minting with attribution tags, and earnings reporting. It works with any MCP client — Claude, ChatGPT, Codex, or your own — and authenticates over OAuth 2.1 with API keys as a fallback.

Do I need an API key to connect?

Not for MCP. An unauthenticated request returns a 401 carrying protected-resource metadata, and clients that support OAuth 2.1 complete an authorization-code flow with PKCE automatically — which is why the setup is a sign-in popup rather than a key to paste. API keys exist for REST clients and for MCP clients with no OAuth support; you issue them under Developers in the dashboard.

Can I use AffiliateOS without an AI assistant?

Yes. Every MCP tool has a REST equivalent under /v1 with API-key auth, plus signed webhooks and a pull-based event feed. n8n workflows, cron jobs and custom code are first-class — MCP is how agents connect, not a dependency.