google-play-developer-mcp

MCPattested
v0.2.0MITUpdated 2d agonpmGitHub

Complete Model Context Protocol (MCP) server for Google Play — 157 tools, full Android Publisher API v3 + Play Developer Reporting v1beta1. Edits, store listings, monetization, in-app purchases, subscriptions, reviews, orders, crash/ANR/error reporting. W

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
40Downloads/wk
8GitHub stars
4Forks
2d agoLast update
Package
Author
LicenseMIT
Version0.2.0
Sourcenpm+mcp-registry
npmgoogle-play-developer-mcp
GitHubdevinwang/google-play-developer-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · ffe25df
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface40 tools · 9 privileged
Security scan✓ Cleanv0.2.0 · todayHow well does this scan work?
EvalsNone
IndexedOct 22, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

40 tools · 9 privileged
Statically extracted from the published packagev0.2.0 · 9h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

accounts_listNo description published

This tool published no description. Forge does not invent one.

accounts_currentNo description published

This tool published no description. Forge does not invent one.

accounts_addNo description published

This tool published no description. Forge does not invent one.

accounts_removeprivilegedNo description published

This tool published no description. Forge does not invent one.

accounts_switchNo description published

This tool published no description. Forge does not invent one.

accounts_updateNo description published

This tool published no description. Forge does not invent one.

apps_listNo description published

This tool published no description. Forge does not invent one.

apps_getNo description published

This tool published no description. Forge does not invent one.

auth_statusNo description published

This tool published no description. Forge does not invent one.

bundles_listNo description published

This tool published no description. Forge does not invent one.

bundles_uploadprivilegedNo description published

This tool published no description. Forge does not invent one.

apks_listNo description published

This tool published no description. Forge does not invent one.

apks_uploadprivilegedNo description published

This tool published no description. Forge does not invent one.

apks_add_externally_hostedNo description published

This tool published no description. Forge does not invent one.

deobfuscation_files_uploadprivilegedNo description published

This tool published no description. Forge does not invent one.

expansion_files_getNo description published

This tool published no description. Forge does not invent one.

expansion_files_uploadprivilegedNo description published

This tool published no description. Forge does not invent one.

expansion_files_updateNo description published

This tool published no description. Forge does not invent one.

expansion_files_patchprivilegedNo description published

This tool published no description. Forge does not invent one.

device_tier_configs_listNo description published

This tool published no description. Forge does not invent one.

device_tier_configs_createNo description published

This tool published no description. Forge does not invent one.

device_tier_configs_getNo description published

This tool published no description. Forge does not invent one.

app_recovery_listNo description published

This tool published no description. Forge does not invent one.

app_recovery_createNo description published

This tool published no description. Forge does not invent one.

app_recovery_deployNo description published

This tool published no description. Forge does not invent one.

app_recovery_cancelNo description published

This tool published no description. Forge does not invent one.

app_recovery_add_targetingNo description published

This tool published no description. Forge does not invent one.

generated_apks_listNo description published

This tool published no description. Forge does not invent one.

generated_apks_downloadNo description published

This tool published no description. Forge does not invent one.

system_apks_variants_listNo description published

This tool published no description. Forge does not invent one.

system_apks_variants_createNo description published

This tool published no description. Forge does not invent one.

system_apks_variants_getNo description published

This tool published no description. Forge does not invent one.

system_apks_variants_downloadNo description published

This tool published no description. Forge does not invent one.

internal_app_sharing_upload_apkprivilegedNo description published

This tool published no description. Forge does not invent one.

internal_app_sharing_upload_bundleprivilegedNo description published

This tool published no description. Forge does not invent one.

edits_insertNo description published

This tool published no description. Forge does not invent one.

edits_getNo description published

This tool published no description. Forge does not invent one.

edits_validateNo description published

This tool published no description. Forge does not invent one.

edits_commitNo description published

This tool published no description. Forge does not invent one.

edits_deleteprivilegedNo description published

This tool published no description. Forge does not invent one.

0 of 40 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Complete Model Context Protocol (MCP) server for Google Play — 157 tools, full Android Publisher API v3 + Play Developer Reporting v1beta1. Edits, store listings, monetization, in-app purchases, subscriptions, reviews, orders, crash/ANR/error reporting. W

Keywords
mcpmcp-servermodel-context-protocolgoogle-playgoogle-play-consolegoogle-play-developer-apiplay-developer-apiplay-developer-reportingandroid-publisherandroidandroid-appplay-storein-app-purchasesplay-purchasessubscriptionsplay-billingmonetizationclaudecursorvscodecodexgemini-cliwindsurfagenticai-assistantautomationai
Alternatives
Comparing tool surfaces…

Tools exposed

40 tools · 9 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-22 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

76 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+64 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.