What it does
App Console exposes Google Play Console tools for releases, track uploads, rollouts, reviews, vitals, listings, subscriptions and screenshots. For App Store Connect it covers versions, builds, submissions, reviews, sales and screenshots. For AdMob it provides earnings and campaign reports, ad sources, ad units and mediation groups. Each tool is available both as an MCP tool and as an appconsole CLI command with identical output, and responses are short plain text rather than browser screenshots or page snapshots.
It suits anyone who manages app releases or monetisation from a terminal, from Claude Code or Claude Desktop, or from scripts and CI. It can be installed as Claude Code plugins for each service, as a single MCP server for other clients such as Cursor, Codex or VS Code, or used from the CLI alone. It is also built into Alchemist Coder. Tools that change something are dry runs unless confirm=true is passed; for Google Play, a dry run builds the change in a draft edit and lets Google validate it before discarding it.
Running it requires uv. Each service needs its own credentials: a Google Play service account JSON key with the relevant permissions in Play Console, an App Store Connect team API key with its Key ID and Issuer ID, and a Google user authorisation for AdMob. Settings are read from environment variables first, then from a local config file with restricted permissions, and the appconsole doctor command checks all three services.
Limitations and requirements
Requires uv. Google Play needs a Google Cloud project with the Play Developer APIs enabled, a service account and specific Play Console permissions; user management needs a further permission. App Store Connect needs a team API key whose .p8 file can be downloaded only once; the Sales function requires the Sales or Finance role. AdMob does not accept service accounts and needs a Google user OAuth consent screen set to In production, because refresh tokens for apps left in Testing expire after 7 days. Some AdMob methods have limited access: Google must enable the publisher id, and the token needs the admob.monetization scope.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
App Console: Google Play, App Store Connect, AdMob
Google Play Console, App Store Connect and AdMob via official APIs: releases, reviews, vitals, ads
v0.3.0As shown on registry.modelcontextprotocol.io when we last read it