A
licenseNot graded
qualityD
maintenanceMCP server for managing Google Play app deployment and in-app products via the Android Publisher API v3.
6 npm
6
MIT
google-play-developer-mcp
by devinwang
Related Servers
Alternatives to google-play-developer-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that connects AI assistants to the Google Play Developer API for automated app publishing, subscription management, review monitoring, and tester management.MIT
- AlicenseAqualityAmaintenanceAn MCP server that connects to the Google Play Developer API to deploy apps, manage releases, respond to reviews, and monitor app health through an AI assistant.123157 PyPI28MIT
- AlicenseNot gradedqualityBmaintenanceEnables authenticated remote MCP clients to manage Google Play apps through the Google Play Developer API, with 117 original tools for publishing releases, editing listings, managing testers, and replying to reviews. Adds remote file uploads and persistent background jobs via Google OAuth sign-in and an allowlist.1MIT
- AlicenseNot gradedqualityAmaintenanceGoogle Play Console MCP server — lets AI agents manage releases, track rollouts, reply to reviews, and pull crash/acquisition reports directly from Google Play Console.26 npm1MIT
- AlicenseAqualityCmaintenanceAn MCP server that drives Google Play releases: bundle upload, track releases (internal/closed/open/production), listing metadata, store graphics, and review replies.8MIT
TDQS
C2.8/5.0
Scored across 157 tools
Disambiguation4/5
The vast majority of tools use clear resource_action naming (e.g., subscriptions_create, tracks_patch, orders_refund), so boundaries are mostly clean. However, a few genuine overlaps exist, notably apps_list vs reports_apps_search (both 'list every app the account can access') and the dense family of subscriptions/onetime_products batch variants that an agent could easily confuse.
Naming Consistency4/5
Strongly consistent snake_case with a resource_prefix_action pattern across nearly all 157 tools. Minor deviations like auth_status, monetization_convert_region_prices, and mixed onetime_products_/subscriptions_ prefixes (singular vs plural asymmetry) keep it from a perfect score.
Tool Count2/5
157 tools is far beyond the 15-25 comfortable range and imposes heavy selection overhead even for a large API. The domain is genuinely broad so not an absolute mismatch, but the surface is bloated with many fine-grained batch/state variants that could be consolidated.
Completeness5/5
Coverage is remarkably thorough across accounts, apps, edits, listings, images, bundles/APKs, tracks, testers, products, subscriptions, base plans, offers, purchases, orders, reviews, users/grants, recovery, and reporting. Full CRUD plus batch and lifecycle state operations are present with few obvious dead ends.
Maintenance
ActivityMaintained
ResponsivenessNo issues