Admob MCP Server

MCP server for the Google AdMob API — apps, ad units, mediation, and revenue reports. Exposed over MCP by the admob mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Ask your AI assistant about your AdMob apps and earnings — in plain language:

• Everything the AdMob API opens to normal accounts — — 9 tools across accounts, apps, ad units, reports, and mediation (why there are no write tools)
• Reports made readable — — streaming report responses are flattened into simple row tables, and monetary values (micros) are converted to real currency units
• Read-only by design — — the sign-in requests read scopes only, so the server cannot change anything in your AdMob account
• Toolsets — — enable only the tool groups you need, e.g. --toolsets reports,accounts
• Three authentication options — — one-command browser sign-in (npx admob-mcp-server auth), environment-variable refresh token, or gcloud Application Default Credentials
• Built-in analysis prompts — and report-spec reference resources

Its toolset

Everything the assistant can do here goes through one of these:

• Toolset — Tools
• accounts — list_accounts, get_account
• apps — list_apps
• adunits — list_ad_units
• reports — generate_network_report, generate_mediation_report, generate_campaign_report
• mediation — list_ad_sources, list_adapters
• Requirements — The Requirements tool exposed by this server

Configuration

You will need 3 environment variables: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REFRESH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18 or newer — check with node --version; if missing, install from nodejs.org - An AdMob account and the Google account that owns it

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at admob-mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Admob's toolset — Toolset, accounts, apps and 4 more — is a fair guide to whether it matches your workflow. It is maintained by ParkSangGwon; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Admob's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the admob mcp server does with a few real requests.