playstore-release-mcp
Related Servers
Alternatives to playstore-release-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for managing Google Play app deployment and in-app products via the Android Publisher API v3.23 npm4MIT
- AlicenseNot gradedqualityDmaintenanceA CLI + bundled MCP server for managing Google Play Console metadata, screenshots, one-time products, and subscriptions from YAML files.12 npmMIT
- AlicenseBqualityAmaintenanceUnified MCP server for App Store Connect & Google Play Console — manage listings, screenshots, releases, reviews & submissions91330 npm35MIT
- 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.43 npm1MIT
- AlicenseAqualityCmaintenanceAn MCP server that drives the full App Store release cycle for iOS and macOS apps: version bump, archive + TestFlight upload, metadata, review submission, and status.832 npmMIT
- 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
TDQS
Scored across 8 tools
Each tool targets a distinct action or resource: config verification, track status, bundle upload, releasing, listing text update, graphics upload, review listing, and reply. There is no overlap or ambiguity between them.
All tools share the 'play_' prefix and most follow a verb_noun pattern (upload_bundle, release_to_track, update_listing, list_reviews, reply_review). 'play_app_status' is a noun phrase rather than a verb action, which is a minor deviation, but the overall pattern is consistent and predictable.
8 tools is well-scoped for a Play Store release management server. Each tool covers an essential operation without redundancy, and the count fits comfortably within the typical 3-15 range.
The surface covers the core release lifecycle (upload, release, status) and store presence (listing text, graphics, reviews). Gaps include inability to read current listing text or images, adjust staged rollout percentages, or manage closed testers, but the primary workflows are sufficiently covered.