search
AppLovin MCP connects the AppLovin Ads platform to AI assistants (e.g. Claude Desktop, Claude Code, Cursor, etc.) using the Model Context Protocol (MCP), an open standard for letting AI tools securely access external data and take action on your behalf.
Once connected, you can manage campaigns and pull reporting by describing what you want in natural language without clicking through the dashboard.
Limited beta. The AppLovin MCP and Campaign Management API is whitelist-only. Contact your AppLovin account team to request access.
Sign in to AppLovin Ads Manager at ads.applovin.com and open Account → API keys. Both your Campaign Management API key and Reporting API key are listed there — copy them from the page.
Only account Admins have access to this page. If you are not an Admin user, contact your Admin for keys access.
Anyone with these keys can read and modify your campaigns. If a key leaks, revoke it from the dashboard immediately.
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.
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"applovin-mcp": {
"command": "npx",
"args": ["-y", "applovin-mcp@latest"],
"env": {
"APPLOVIN_CAMPAIGN_MANAGEMENT_API_KEY": "«YOUR_MANAGEMENT_KEY»",
"APPLOVIN_REPORTING_API_KEY": "«YOUR_REPORTING_KEY»"
}
}
}
}Run once in your terminal:
claude mcp add applovin-mcp \
--env APPLOVIN_CAMPAIGN_MANAGEMENT_API_KEY=«YOUR_MANAGEMENT_KEY» \
--env APPLOVIN_REPORTING_API_KEY=«YOUR_REPORTING_KEY» \
-- npx -y applovin-mcp@latest
Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):
{
"mcpServers": {
"applovin-mcp": {
"command": "npx",
"args": ["-y", "applovin-mcp@latest"],
"env": {
"APPLOVIN_CAMPAIGN_MANAGEMENT_API_KEY": "«YOUR_MANAGEMENT_KEY»",
"APPLOVIN_REPORTING_API_KEY": "«YOUR_REPORTING_KEY»"
}
}
}
}
After you save the config, restart your assistant so it retrieves the new MCP server.
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:
If you get sensible output from any of these, you’re connected. If you see tool not found or nothing happens, see Troubleshooting below.
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.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).
node --version.@latest pin forces an update on every launch — restart your assistant.npx clear-npx-cache and restart again. Include the Trace ID from the error if you contact support.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.
Cookie Settings