get started

two tracks.
one local server.

Choose the path that matches how you want to set up affiliate-mcp. Both keep your credentials and affiliate data on your machine.

track 1 · non-technical

claude desktop .mcpb

Install the host-native extension. Claude owns the runtime, configuration, and secure credential fields, so no Node.js, terminal, or separate setup app is required.

Secure setup fields currently cover Awin, CJ, Impact, and Partnerize. Adding other networks uses the technical track until portable browser setup ships.

download the Claude extension ▸
track 2 · technical

cli + local stdio

Use the complete setup wizard, test your credentials, then connect through a host-native package, CLI installer, or local stdio configuration.

follow the technical track ▾

The standalone Electron/DMG setup app is a fixes-only compatibility fallback for existing macOS users, not a third primary track.

00

technical track: what you need

node 20+

A free runtime. Grab it from nodejs.org if you don't have it.

your logins

The accounts you already use for the affiliate networks you're on. Nothing new to sign up for.

claude or codex

Claude Desktop, Claude Code, or Codex installed. That's where you'll ask the questions.

01

run the setup wizard

Open Terminal (Mac) or PowerShell (Windows), paste the line, press enter. It walks you through one network at a time and shows exactly where to find each login.

terminal
$ npx affiliate-networks-mcp setup ? which network? Awin ? which side? publisher ? paste your API token •••••••••••• checking against Awin… ok ✓ publisher id 123456 found ? add another network? no saved → ~/.affiliate-mcp/.env (mode 0600, your machine only)
02

check it's wired up

One line per network: ok for healthy, or a plain reason if something's off.

terminal
$ npx affiliate-networks-mcp test Awin ok CJ Affiliate ok Rakuten error — token expired, re-run setup
03

connect it to your ai

Pick a shipped client path. The wizard offers these automatically at the end, too.

terminal
?

client support states

  • shipped + testedClaude Desktop .mcpb, Claude Desktop CLI/manual config, Claude Code, and Codex have repository-owned setup paths and automated validation. This does not claim live proof against every host version. The .mcpb is the primary non-technical path.
  • partially shippedClaude Cowork uses a private-mirror flow and requires org-admin follow-through.
  • possible, untestedCursor, VS Code, and generic local MCP clients can be compatible with the local stdio server, but do not yet have a tested first-party setup journey here.
  • planned, not shippedPortable browser credential setup and a remote HTTPS MCP path for ChatGPT require separate reviewed implementation. ChatGPT cannot use the local stdio server directly.
04

ask it anything

Open a new conversation and check it's connected. You should see every network you set up.

what you'll see
Claude✳ affiliate · connected
what affiliate networks do you have access to?

You're connected to 3 networks:

Awin · publisherCJ Affiliate · publisherRakuten · publisher

Ask me anything — earnings, pending commissions, link audits, or a report.

?

stuck?

  • "…returns nothing"The server's loaded but credentials are missing. Ask "help me set up my affiliate network credentials", or re-run npx affiliate-networks-mcp setup.
  • "unknown skill: plugin"The plugin commands are shell commands, not chat. Run them in your terminal, not inside the conversation.
  • stale versionForce a fresh fetch with npx --yes affiliate-networks-mcp@latest.