Chat with your affiliate-network data in Claude through a local MCP server. 80+ publisher and advertiser-side adapters across the US, EU, Nordics, APAC and LatAm, most experimental.
Use this skill when the user asks how much they have earned across their configured affiliate networks, or wants a consolidated period summary. Trigger on: "show my affiliate earnings", "what did I earn last month?", "earnings report", "how much have I made?".
Use this skill when the user is trying to set up a specific affiliate network and needs help finding credentials, navigating the dashboard, or understanding the setup steps. Trigger on: "help me set up Awin", "how do I get a CJ API token", "setup help", "I'm stuck on Impact setup".
Use this skill when the user wants a health check of their configured affiliate networks — auth, reachability, supported operations. Trigger on: "is my affiliate setup working", "check my affiliate networks", "are all my networks responding", "network health".
Use this skill when an agency operator wants a single headline view of revenue across every brand and every network in their book — the agency's home dashboard. Trigger on: "How is the whole book doing this week?", "Show me revenue across all clients", "Portfolio summary", "Which brands are trending down this month?".
Use this skill when the user wants to verify that the affiliate links on their site, in a draft, or in a sitemap are still pointing at active programmes. Trigger on: "audit my affiliate links", "check my links still work", "find broken affiliate links", "verify my links track properly".
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Integrate your affiliate networks with Claude or Codex.
Network operators: most adapters are community-built and
experimental. Adoption gives your team ownership and a verification path; promotion topartialorproductionstill requires current evidence and maintainer review. Find your network's issue under theadopt-this-networklabel.
Affiliate networks have two sides — and neither has a first-class AI workspace integration.
Publishers earn commissions from the programmes they join. Brands (and the agencies who manage them) run those programmes and pay the commissions out. I wanted to chat to my own affiliate data in the AI workspace I already use; none of the networks had shipped an integration for either side, so I built a broad beta set that covers both publisher and advertiser-side work.
If you're a publisher, you can ask:
"What did I earn across all networks last month?"
"Which programmes have transactions still pending after 90 days?"
"Compare my earnings month on month."
If you're on the brand side — running a programme, or an agency managing several — you can ask:
"How is Acme's programme doing this quarter?"
"Show me revenue across all my clients this week."
"Any anomalies in the affiliate data?"
Your AI workspace figures out which networks to call, fetches the data live from their APIs, and gives you the answer. You can use Claude or Codex to turn it into a sheet, an artifact, an email to your boss, whatever you want.
Free and open source. MIT licensed. Bring your own keys. For the product philosophy, read the AI-native affiliate data manifesto.
This tool serves two audiences. Pick the one that fits — or both, if you wear both hats.
You're a publisher. You earn commissions from affiliate programmes, your dashboards can't keep up with how fast you can think, and you want one conversation that spans every network you're on.
You're on the brand side. You run an affiliate programme — or you're an agency managing several brands' programmes. You want one question that fans out across networks and brands, and surfaces what the dashboards bury: publishers trending down, reversal spikes, dead links, programmes drifting toward zero.
Either way, you do not need to know what an API is or write code. The non-technical Claude Desktop track needs:
The technical track uses a terminal, Node.js 20 or newer, and Claude Desktop, Claude Code, Codex, or another compatible local stdio MCP client; check the support states below before relying on an untested client journey.
And if you work for an affiliate network, this is also for you. The
bundled adapters are placeholders until each network adopts its own. See
CONTRIBUTING.md under "Adopting your network".
One question, every network and every brand. "Show me earnings by programme" hits your configured publisher networks in parallel. On the brand side, "show me revenue across all my clients this week" fans out across every brand and network pair you've registered.
Plain English, not filters. No more clicking through date pickers and saved views. "Last quarter, status pending, sorted by amount" is the whole prompt.
Your data, your machine. It runs locally. Your keys live in
~/.affiliate-mcp/.env, locked to your user account. There is no hosted
account. Optional anonymous usage telemetry is off by default and never
contains affiliate data, credentials, prompts, arguments, results, or error
text. The networks see the same API calls they'd see from their dashboard.
Catches what dashboards bury. Stale transactions, inactive programmes, dead deeplinks and week-on-week drops are surfaced by the packaged skills.
Optional local result cache. Persistent caching is off by default. Set
AFFILIATE_MCP_CACHE=on in ~/.affiliate-mcp/.env to cache selected programme
inventory and closed reporting windows locally with owner-only permissions.
Open and current windows always go live. On a shared machine where you cannot
rely on file permissions, leave caching off. Run
affiliate-networks-mcp cache clear to remove cached results; see
PRIVACY.md for the storage and retention contract.
npx claudepluginhub bobberrisford/affiliatemcp --plugin affiliate-networks-mcpGive your AI a memory — mine projects and conversations into a searchable palace. 33 MCP tools, auto-save hooks, and guided setup.
MCP server that saves 98% of your context window with session continuity. Sandboxed code execution in 11 languages, FTS5 knowledge base with BM25 ranking, and automatic state restore across compactions.
Write SQL, explore datasets, and generate insights faster. Build visualizations and dashboards, and turn raw data into clear stories for stakeholders.
Open-source, local-first Claude Code plugin for token reduction, context compression, and cost optimization using hybrid RAG retrieval (BM25 + vector search), reranking, AST-aware chunking, and compact context packets.
Agent Skills for AI/ML tasks including dataset creation, model training, evaluation, and research paper publishing on Hugging Face Hub
Excalidraw diagramming toolkit — auto-diagram any codebase, architecture diagrams, data flows, with PNG/SVG/URL export