A
licenseNot graded
qualityD
maintenanceMCP server that connects AI assistants to the Google Play Developer API for automated app publishing, subscription management, review monitoring, and tester management.
MIT
play-store-mcp
by lusky3
Related Servers
Alternatives to play-store-mcp
No user-submitted related servers found.
Related Servers
- 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.85 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that exposes Google Play Console analytics to AI agents, including store-listing acquisitions by traffic source, installs, uninstalls, ratings, crashes, subscriptions, and reviews by reading bulk CSV reports from Cloud Storage.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for managing Google Play app deployment and in-app products via the Android Publisher API v3.9 npm4MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides AI agents with tools to build, deploy, and manage Flutter applications, including APK/AAB generation, keystore management, and CI/CD integration.5 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
A3.8/5.0
Scored across 3 tools
Disambiguation5/5
Each tool occupies a clearly separate stage of the workflow: search discovers tools, get_schema inspects parameters, and execute runs the actual call. There is no overlap or ambiguity between them.
Naming Consistency4/5
Tool names are all lowercase and verb-focused, with get_schema following verb_noun while search and execute are bare verbs. The pattern is mostly predictable but not perfectly uniform.
Tool Count4/5
Three tools is minimal but exactly matches the intended meta-workflow of discover, inspect, and execute. Each tool clearly earns its place, though the set is on the smaller end.
Completeness4/5
The workflow covers the full lifecycle from discovery to execution, enabling an agent to find and call tools effectively. A dedicated list-all-tools capability is missing, but search compensates for that gap.
Maintenance
ActivityNo data
ResponsivenessResponsive