Ask your Affise account a question and get the answer straight away — no CSV export, no dashboard tabs to hunt through. 25 read-only tools cover stats, offers, conversions and partners.
> Which offers grew fastest in DE last week? Reading Affise · affise_stats_compare 18–24 Aug vs 11–17 Aug · slice: offer, country=DE OFFER REVENUE Δ 1180 Finance DE $48,210 +38% 2077 Gaming DE $31,904 +21% 1642 Utilities DE $12,455 −6% Revenue in DE is up 24% week over week, almost all of it offer 1180 — three new partners started running it on Wednesday.
Built for the 1,000+ partner-marketing teams already running Affise
Four fields and a sign-in. No config file, no client ID, no secret — the connection registers itself.
Any Claude account on a plan with connectors — claude.ai, Claude Desktop or the mobile apps.
In claude.ai, click your name in the bottom-left corner, then Settings ▸ Connectors. Claude Desktop uses the same path.
Scroll to the end of the connector list and click Add custom connector.
Put the URL above into Remote MCP server URL and name it Affise. Leave the advanced OAuth fields empty.
Click Connect, sign in, approve. The window closes itself and the connector reads as connected.
Check it worked. Ask “Using Affise, run a status check.” A working connection answers with your Affise base URL and an OK status.
Full guide, with troubleshooting →Every guide is the same shape: the exact menu path, the URL to paste, and what a working connection looks like. None takes more than two minutes.
claude.ai, Claude Desktop and the mobile apps — OAuth sign-in, no config file.
Setup guide →The terminal agent — one claude mcp add command, OAuth in the browser.
Plus, Pro, Business and Enterprise — via developer mode or a workspace connector.
Setup guide →Query Affise from the editor — one entry in mcp.json.
Windsurf, Cline, Continue, VS Code, custom agents — plus the local stdio install.
Setup guide →These are real asks, typed the way you would say them out loud. The server works out which slice, filter and date range each one needs.
This is the complete surface your assistant gets. Nothing here can create, edit or delete anything in Affise — the tools are declared read-only to your client, so it can call them without asking permission every time.
| affise_stats | Ask for stats in plain English — periods, breakdowns and top-N are resolved for you. | Read-only Any |
| affise_stats_raw | Precise aggregate pulls with explicit slices, fields and filters. | Read-only Any |
| affise_stats_compare | Period over period, with the range auto-aligned so month-to-date compares like for like. | Read-only Any |
| affise_trafficback | Rejected and redirected traffic broken down by reason, geo and partner. | Read-only Any |
| affise_affiliate_analysis | One-call account review for a single affiliate: KPIs, per-offer breakdown, insights. | Read-only Admin |
| affise_retention_rate | Cohort retention across follow-up events for one offer. | Read-only Admin |
| affise_time_to_action | Click-to-conversion latency distribution for one offer. | Read-only Admin |
| affise_conversions_raw | Per-event conversion rows with IP, geo, device, sub1–sub8 and custom fields. | Read-only Any |
| affise_get_conversion | The complete record for one conversion by ID. | Read-only Admin |
| affise_search_offers | Natural-language offer search — “gaming offers for US mobile traffic”. | Read-only Any |
| affise_smart_search | Offer search that resolves categories for you and suggests near matches. | Read-only Any |
| affise_get_offer | Full detail for one offer: payouts, caps, targeting, status. | Read-only Any |
| affise_offer_categories | Every offer category configured on your account. | Read-only Any |
| affise_offer_tracking_link | Build a tracking link for an offer × affiliate, with sub1–sub8 appended. | Read-only Admin |
| affise_list_partners | Paginated affiliate roster with country, status and search filters. | Read-only Admin |
| affise_get_partner | The full affiliate record for one partner ID. | Read-only Admin |
| affise_list_advertisers | Paginated advertiser list, optionally with offer counts. | Read-only Admin |
| affise_get_advertiser | The full advertiser record for one advertiser ID. | Read-only Admin |
| affise_partner_profile | The signed-in affiliate’s own profile, manager and permissions. | Read-only Partner |
| affise_partner_balance | The signed-in affiliate’s multi-currency balance by type. | Read-only Partner |
| affise_partner_offers | Offers the affiliate can request access to. | Read-only Partner |
| affise_partner_live_offers | Offers the affiliate is currently running. | Read-only Partner |
| affise_partner_find_subs | Discover which sub-ID values the affiliate has actually used. | Read-only Partner |
| affise_partner_news | Platform announcements visible to the affiliate. | Read-only Partner |
| affise_authenticate | Opens an inline form to enter or rotate your Affise credentials. | Read-only Any |
Admin tools need an admin API key · Partner tools work with an affiliate’s own key · Any works with either.
Use the endpoint we host, or run the open-source server on your own machine. Both expose the identical toolset.
A managed, always-on HTTPS endpoint. Nothing to install and nothing to keep up to date — point your client at the URL and sign in.
Run it yourself when you would rather have nothing in the path. Data flows only between your machine and the Affise API.
No API integration to build. Your assistant becomes the interface.
Paste https://mcp.affise.com/mcp into your client’s connector settings. The setup guides show the exact menu path for each one.
A browser window opens for OAuth 2.0 sign-in. Your credentials are encrypted into a session only your requests can read.
Your assistant picks the right tool, pulls the data and answers. Ask follow-ups the way you would ask a colleague.
Read-only MCP tools
Clients with setup guides
Browser sign-in, no config
Rate limit per IP
The server holds no copy of your data. It forwards each request to the Affise API under your own credentials and returns the answer.
All 25 tools are read-only and declared as such to your client. There is no code path that writes to Affise.
Your Affise credentials are encrypted per user. Static bearer tokens are available for automation.
The server sees exactly what your API key sees. An affiliate key reaches only that affiliate’s own data.
Run the open-source server locally and no third party sits between you and the Affise API.
Affise is SOC 2 certified. The MCP server inherits that posture — it reaches your data only through scoped API access.
Exactly what this server receives, what it stores, for how long, and who else sees it is set out in the MCP data notice — written for the server, not the website.
{
"name": "affise_stats_raw",
"title": "Affise Stats (Raw)",
"annotations": {
"readOnlyHint": true,
"destructiveHint": false,
"idempotentHint": true,
"openWorldHint": true
}
}
# Every tool carries these hints, so your
# client knows nothing here can mutate data.
Connect your assistant once and ask your Affise account questions the way you would ask an analyst.