mcpdirectory.dev
9,129 servers · updated 23 Sept

Affiliate Networks MCP server

community Active last commit 43 d 
{
  "mcpServers": {
    "affiliate": {
      "command": "npx",
      "args": [
        "-y",
        "affiliate-networks-mcp@latest",
        "affiliate-networks-mcp"
      ]
    }
  }
}
file .mcp.json (in your project root)install npx -y affiliate-networks-mcpversion 0.19.0

What it does

This server connects affiliate networks to Claude and Codex, letting publishers and brands query their affiliate data across multiple networks in plain language. It runs locally with your own API keys and supports 72 networks through community-built adapters.

  • Publishers can ask cross-network questions like "What did I earn across all networks last month?" or "Which programmes have transactions still pending after 90 days?"
  • Brand-side users running affiliate programmes can query "How is this programme doing this quarter?" or "Show me revenue across all my clients this week" across multiple networks.
  • Spot data anomalies and trends that dashboards bury, such as stale transactions, inactive programmes, or week-on-week performance drops.

Tools this server exposes

ToolDoes
affiliate_queryQuery earnings, transactions, and programme data across configured affiliate networks using natural language.
network_statusCheck which affiliate networks are configured and available for querying.
cache_managementClear or manage cached affiliate programme inventory and reporting data.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.