Best for
- Affiliate publishers who want natural-language access to multiple networks
- Agencies managing multiple brands' programs
- Teams needing periodic reporting and anomaly monitoring
A
Affiliate Networks MCP
Community
Ask your affiliate networks in plain English from your AI workspace.
GitHub source repository ↗
70FMRS · B
Community-driven open-source MCP server to integrate affiliate networks into AI workspaces. It offers broad adapter coverage but most are experimental, so caution is advised. Main strength is covering both publisher and advertiser sides, though advertiser side is read-only. A useful tool for marketers wanting to simplify affiliate data queries.
Affiliate Networks MCP is a local MCP server that lets you query multiple affiliate networks (both publisher and advertiser sides) using natural language. It supports over 80 network adapters, most community-built and experimental. Your credentials stay local in ~/.affiliate-mcp/.env. Includes skills for consolidated earnings, anomaly detection, and reports. Aimed at publishers, brands, and agencies who want to chat with their affiliate data.
Setup
Technical track: install Node.js 20+, run npx affiliate-networks-mcp setup to configure credentials interactively, then npx affiliate-networks-mcp test to verify. Use npx affiliate-networks-mcp install to auto-configure Claude Desktop or Codex. For Claude Code, run claude plugin marketplace add bobberrisford/affiliatemcp and claude plugin install affiliate-networks-mcp@affiliatemcp. Non-technical users can download the .mcpb file and install in Claude Desktop. Also available via hosted connector at mcp.agenticaffiliate.ai (paid, OAuth).
Fit and risk
Not for
- Users without an AI client (e.g., Claude Desktop)
- Advertisers needing write operations (e.g., link creation) since advertiser adapters are read-only
- Clients that are not yet officially supported (e.g., Cursor, VS Code) without testing
- Networks where clicks are essential, as many adapters lack click support
Required permissions
- Credentials for network APIs (API keys, tokens, etc.)
- Optional: local file write to `~/.affiliate-mcp/.env` and `brands.json`
- Optional: anonymous usage telemetry (off by default)
- Optional: local result cache (off by default; writes files when enabled)
Risks and side effects
- Experimental community adapters may be unreliable or return inaccurate data.
- Credentials stored in local files; risk if file permissions are loose or device compromised.
- Hosted connector stores credentials in encrypted vault but involves third-party service.
- API calls may incur rate limits or costs depending on the network.
- Untested client paths may not work; check support status table.
Troubleshooting
- If queries return nothing, check credentials are configured: run `npx affiliate-networks-mcp setup` or trigger the `affiliate-network-setup-help` skill.
- If stale npm cache, run `npx --yes affiliate-networks-mcp@latest` to fetch latest.
- If Cowork rejects the repository, ensure it's private or run `cowork-mirror` to create a private mirror.
- If a specific network fails, run `npx affiliate-networks-mcp doctor <network>` for diagnostics.
- Ensure API keys have no trailing spaces and tokens are not expired.
Use cases
Publisher asks 'What did I earn last month?' across all networks
Brand-side user asks 'How is Acme performing this quarter?'
Agency asks 'Show me revenue across all my clients this week.'
Ask 'Any anomalies in the affiliate data this week?'
Supported clients
Claude DesktopFull support
Claude CodeFull support
CodexFull support
Claude CoworkPartial support