AppLovin MCP

Manage your AppLovin Ads Manager campaigns and pull reporting through natural conversation with any MCP-compatible assistant.

Limited beta. The AppLovin Axon Campaign Management API is whitelist-only. Contact your AppLovin account team to request access.

What you’ll need

• An AppLovin Axon Campaign Management API key and Reporting API key, both for the same AppLovin Ads Manager account
• An MCP-compatible assistant — Claude Desktop, Claude Code, Cursor, or any other client that supports MCP

Step 1 — Get your API keys

Sign in to AppLovin Ads Manager at ads.axon.ai and open Account → API keys. Both your Campaign Management API key and Reporting API key are listed there — copy them from the page.

Step 2 — Connect your assistant

Pick the snippet for your assistant. You only need one.

With other MCP-compatible clients, use the same launch command — npx -y applovin-mcp@latest — and pass the two API keys as environment variables.

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

Claude Code

Run once in your terminal:

Cursor

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):

Step 3 — Try it

Anything you normally do manually in the dashboard, ask MCP to do for you!

Not sure where to start? Here are a few commands to try:

• “List my five most recent campaigns in AppLovin Ads Manager.”
• “Adjust the budget on my biggest campaign to $5000/day.”
• “Clone my top-spending campaign and swap in these creative-set URLs.”
• "Create a discovery campaign with a 100% ROAS. Use the same ads and creative set structure as my top spending campaign."
• “Upload these five videos and attach them to my creative sets: [INSERT URL].”
• “Pull last week’s ROAS by campaign.”

If you get sensible output from any of these, you’re connected. If you see tool not found or nothing happens, see Troubleshooting below.

Configuration

• APPLOVIN_CAMPAIGN_MANAGEMENT_API_KEY (required) — your management API key.
• APPLOVIN_REPORTING_API_KEY (required) — your reporting API key, from the same account.
• APPLOVIN_READONLY (optional, default false) — set to true to disable all write tools — this is useful if you want the assistant to read but not modify campaigns.

Safety

AppLovin MCP is a typed wrapper over the public AppLovin Axon API. It returns data and forwards your writes — it doesn’t provide campaign strategy. Any optimization suggestion from the assistant is the LLM’s interpretation, not an official AppLovin recommendation.

You’re responsible for all actions taken against your account through this tool. Review what the assistant proposes before approving any potentially disruptive operations (pauses, budget changes, deletes).

Troubleshooting

Assistant doesn’t see the server

• Restart your assistant after you edit its config.
• Confirm Node 22+ is installed: node --version.

401 / 403 authentication errors

• Both keys must belong to the same AppLovin Ads Manager account. Double-check you copied each one fully.

“Schema mismatch” or “unrecognized key”

• This usually means the AppLovin Axon API added a field. The @latest pin forces an update on every launch — restart your assistant.
• Persists? Run npx clear-npx-cache and restart again. Include the Trace ID from the error if you contact support.

Getting help

For AppLovin Axon API or account questions, contact your AppLovin account team. For MCP issues, share the Trace ID from any error — it lets the team trace your request.

Provided “as is” under the MIT license. © AppLovin Corp.