AppLovin MCP server: Axon ads and MAX revenue in Claude, Codex or Cursor
AppLovin has no MCP server published by AppLovin that we could find at the time of writing (November 2026); community-built servers wrap the Reporting and Campaign Management APIs with your own keys on your machine. This guide covers a hosted setup: connect the account once with its Report Key, add the Campaign Management key if you want changes, and any MCP client reaches it with an Agent Planners key — new campaigns paused, spend decisions held for a person.
What already exists for this platform
AppLovin exposes its data through keys on the Keys page of the AppLovin dashboard, not a sign-in: a Report Key for the three reporting APIs (Axon ads promoting websites, Axon ads promoting apps, MAX mediation revenue), an Event Key for the Axon Pixel, and a separate Campaign Management key for the Axon Campaign Management API. At the time of writing we found no MCP server published by AppLovin itself; open-source servers built by third parties wrap these APIs and run with your keys in your own client.
- Three reports, three endpoints. Web, app and MAX are different APIs with different column lists; a column one accepts, another refuses.
- The account is blocked for 24 hours after 100 error answers in 5 minutes (AppLovin's Campaign Management rule). A wrapper that retries a bad request in a loop can lock the account for a day.
- AppLovin ignores status on create and has no delete or archive, so what a wrapper creates is what serves until someone pauses it.
What a hosted layer adds
| A direct API wrapper | Agent Planners MCP | |
|---|---|---|
| AppLovin tools | Whatever the wrapper exposes | 13 reads, 13 writes |
| Where the keys live | In your client's config | Encrypted on our server; your MCP key never carries them |
| Report rules | Discovered by the error | Checked before the call: 88 days back, hour data for 30 days, columns per report |
| Creates | As AppLovin starts them | Paused right after creation and read back |
| A new campaign, a budget or goal change, LIVE, creative sets into campaigns | Applied when called | Held for a person on every key mode |
| Error answers | Counted by AppLovin | Validated first; nothing is retried on a 4xx, and sending stops after 30 errors in 5 minutes |
| Other platforms in the same session | No | Every other platform the workspace connected, on one endpoint |
send_conversion_events (server-side events, a dry run unless asked; a real send waits for a person) — with the Conversion API key. Over MCP the names are applovin__report, applovin__max_revenue_report, applovin__get_account_health, applovin__get_campaigns and so on. A key only sees the writes if it carries tools:write; a key that lists tools on demand reaches them through search_tools and call_tool.How to configure it
- 1In the AppLovin dashboard open your account menu → Keys and copy the Report Key (and the Event Key if you want the Axon Pixel steps).
- 2On Integrations, press Connect with keys on the AppLovin card, name the account (AppLovin's reports do not name it), paste the keys and press Check and save. The Report Key is checked against the three reports before it is stored encrypted.
- 3For changes: copy the Campaign Management key and the numeric account id (Go to settings), then press Add campaign management on the same card.
- 4Create a key in API & MCP:
tools:readfor reporting, addtools:writefor changes. Add the server with the snippet below, rundescribe_permissions, thenapplovin__list_connectionsto get the account to scope each call with.
claude mcp add --transport http agent-planners https://www.agentplanners.com/api/mcp \
--header "Authorization: Bearer ap_live_…"What waits for a person, whatever the key allows
A tools:write key's ordinary AppLovin writes — a rename, targeting, a paused creative set, an asset upload, a pause — either run inside the workspace's guardrails or queue for an admin, depending on how the key was minted. These never run on the key's say-so: they are held in the approval queue, an admin or editor is emailed, and none of them is ever taken by a bulk approval.
- A new campaign — it sets a daily budget and a goal (it is paused after creation either way).
- A budget or goal-value change on a campaign.
- Status LIVE on a campaign or a creative set — that is when delivery and spend can start.
- Creative sets added to campaigns, a creative set created into a campaign, and a clone that is not paused — they can serve at once.
What we measured with a live Report Key
- 88 days back, not 90. A start 88 days back was accepted and 89 days back was refused on all three reports (AppLovin's docs say 90 days for ads and 45 for MAX).
- Columns differ from the docs. The web report refused
generate_lead_«x»; the app report refusedrpi_«x»andpub_revenue_«x». Those are not offered, and an unknown column is refused before the call with the list the report takes. - UTC and US dollars. Days are UTC days, "last 7 days" is the 7 complete days ending yesterday, and spend and revenue come back as AppLovin reports them.
- An empty report is an answer. The account we connected had no delivery in the window, and the tools said so instead of returning zeros as results.
Frequently asked questions
- Is there an official AppLovin MCP server?
- We could not find one published by AppLovin at the time of writing (November 2026). Community-built servers wrap the Reporting and Campaign Management APIs with your own keys; a hosted server like this one stores the keys encrypted, checks AppLovin's rules before each call and holds spend decisions for a person.
- How do I connect Claude to AppLovin?
- Connect the account with its Report Key on Integrations, create an Agent Planners API key, add the MCP endpoint to Claude Code or Claude Desktop, and call applovin__list_connections to get the account to scope each call with.
- Can an MCP client turn on spend in AppLovin?
- Not on its own. New campaigns and creative sets are paused right after creation, and a new campaign, a budget or goal change, status LIVE and adding creative sets to campaigns are held for a person on every key mode.
- How far back can it read AppLovin reports?
- 88 days, in UTC days. Hour-level data covers the last 30 days.