Choose the path that matches how you want to set up affiliate-mcp. Both keep your credentials and affiliate data on your machine.
.mcpbInstall 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.
follow the.mcpb track ▾
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 ▾On both these local tracks your affiliate credentials are API keys, entered once into Claude Desktop's secure fields or the setup wizard, and stored on your machine. You never copy a connection token into Claude's settings. The hosted tier works the same way — you connect Claude to it with a browser sign-in, not a pasted token — and it is a separate, optional product, not required to use affiliate-mcp locally.
The standalone Electron/DMG setup app is a fixes-only compatibility fallback for existing macOS users, not a third primary track. Existing desktop-app users →
No terminal, no Node.js, no config files, and no connection token to paste. Claude Desktop installs the local server, stores your keys in its own secure fields, and wires everything up.
One file, .mcpb. It contains the whole local server.
Open Claude Desktop, then Settings → Extensions → Advanced settings → Install Extension… and pick the file you just downloaded. Claude owns installation, permissions, and secret storage from here.
During install, Claude Desktop shows secure fields for your API credentials and stores them in your operating system's keychain. This is where your keys go: not into a chat box, and not as a pasted token.
Guided fields currently cover Awin, CJ, Impact, and Partnerize. For any other network, run the technical track once and point the extension at that config, until portable browser setup ships.
Claude only loads new tools when it starts. Fully quit Claude Desktop, reopen it, start a fresh chat, and ask "what affiliate networks do you have access to?"
see what you can ask ▸A free runtime. Grab it from nodejs.org if you don't have it.
The accounts you already use for the affiliate networks you're on. Nothing new to sign up for.
Claude Desktop, Claude Code, or Codex installed. That's where you'll ask the questions.
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.
One line per network: ok for healthy, or a plain reason if something's off.
Pick a shipped client path. The wizard offers these automatically at the end, too.
.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.Open a new conversation and check it's connected. You should see every network you set up.
You're connected to 3 networks:
Awin · publisherCJ Affiliate · publisherRakuten · publisherAsk me anything — earnings, pending commissions, link audits, or a report.
npx affiliate-networks-mcp setup.plugin commands are shell commands, not chat. Run them in your terminal, not inside the conversation.npx --yes affiliate-networks-mcp@latest.