applovin-mcp

AppLovin MCP

MCP server for AppLovin Ads Manager (ads.axon.ai) — manage your campaigns and pull reporting through natural conversation with Claude, Cursor, and other MCP-compatible assistants. Wraps the AppLovin Axon Campaign Management API.

Limited beta. Management API Key is currently whitelist-only. If you need access, contact your AppLovin account team.

Requirements

• Node.js 22 or newer (download)
• An AppLovin Axon Campaign Management API key and Reporting API key issued for the same account. Both are obtained from AppLovin Ads Manager (ads.axon.ai → Account → API keys).

Quick start

The server runs on demand via npx — no global install needed. Pinning @latest forces npx to re-check the registry each launch, so you're always on the newest release without having to manage updates manually.

npx -y applovin-mcp@latest

(You won't normally invoke it by hand — your assistant launches it. The command above just verifies you can pull the package.)

Connect your assistant

Pick the snippet for your client and fill in your two API keys.

{
  "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"
      }
    }
  }
}

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

{
  "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 saving, restart your assistant. You should see the applovin-mcp server appear as connected.

Configuration

The server auto-detects whether your account is APP or WEB at startup and registers the matching tool set.

Safety features

• Read-only mode (APPLOVIN_READONLY=true) removes all write tools at startup, so the assistant cannot create, update, or upload even if it tries.
• Upload deny-list — applovin_asset_upload reads from your local disk. Before reading bytes, every path is canonicalized and checked against common-sensitive locations (.ssh/, .aws/, .env, *.pem, *.key, etc.). Symlinks are resolved first.
• Audit log — every upload attempt (allowed or denied) is logged to stderr as a JSON line.

Don't run the server as a user with read access to secrets you don't want it to ever see.

Troubleshooting

The assistant says "tool not found" or the server isn't connecting. Restart the assistant after editing config. Confirm Node 22+ is on your PATH and npx -y applovin-mcp works in a terminal.

"Schema mismatch" or "unrecognized key" errors. Usually the AppLovin Axon API has added a field. Make sure you're on the latest version — the @latest suffix in the snippets above forces npx to re-check the registry on every launch. If you suspect a stale cache, run npx clear-npx-cache (or rm -rf ~/.npm/_npx) and restart your assistant. Include the Trace ID from the error when contacting your AppLovin account team.

Authentication errors (401/403). Both keys must belong to the same AppLovin Ads Manager account. Re-check the keys in your client config.

Disclaimer

This server is a typed wrapper over the public AppLovin Axon Campaign Management API — it returns data and forwards writes. It does not provide platform strategy or "best-practice" guidance; any optimization advice surfaced by your assistant is the LLM's interpretation, not an official AppLovin recommendation. You are responsible for the campaign actions taken against your AppLovin Ads Manager account via this tool. Provided "as is" per the MIT license.

License

Licensed under the MIT License. Copyright 2026 AppLovin Corp.