MCP overview
Ask your assistant about your affiliate program instead of opening the dashboard.
AffiliateRail ships a hosted MCP server, so Claude, ChatGPT and any other MCP-capable assistant can work with your program in plain language: who your top partners are this month, which commissions are waiting for approval over $50, who has gone quiet, why a payout failed. With a write-scoped key it can also act, with your confirmation: approve or reject a commission, decide an application, close a risk flag, invite a partner, tidy the resources shelf, send a campaign.
Server URL: https://mcp.affiliaterail.com/mcp
Included in: every plan, the free trial included.
Why it exists
The dashboard answers the questions we predicted. An assistant answers the ones we did not: "compare my top five partners' revenue this quarter with last", "which idle partners earned money before June", "summarise what happened in the program this week". The MCP server gives the model live, scoped access to your data, so those answers come from your ledger rather than the model's imagination.
Amounts come back as integer minor units with the currency and a formatted string, and the assistant is told to quote the formatted one, so numbers arrive as money, not mystery integers.
Connecting takes about two minutes
You never paste a master key into an assistant. Adding the server sends the assistant to an AffiliateRail sign-in page where you paste an API key once; the assistant receives a short-lived token instead of the key, and revoking the key under Settings, API keys disconnects every assistant that used it, immediately.
Connect Claude or ChatGPT has the step-by-step for both, plus the one-line command for Claude Code.
What it can and cannot do
Sixteen read tools cover partners, customers, commissions, applications, revenue, reports, payouts, flows, referrals, risk, resources and messaging; twelve guarded write tools cover the review queues, invitations, the resources shelf and messaging triggers; two resources describe your program and the webhook event catalogue. The tool reference lists them all with their inputs.
The boundaries are deliberate. Nothing that moves money, mints credentials, deletes data or touches billing is exposed over MCP at all, whatever the key's scopes. Security explains the model, and every write the server does perform lands in your audit log named as the assistant's key.