google-play-vitals-mcp
Related Servers
Alternatives to google-play-vitals-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI agents to manage Google Play Console reviews and Android app releases, including replying to reviews, promoting releases, managing staged rollouts, and checking crash/ANR vitals.4411 npm1MIT
- AlicenseBqualityAmaintenanceEnables managing releases, monitoring Android vitals, analyzing earnings and search terms, optimizing ASO, and preflighting store assets through natural language, with a confirmation gate before destructive writes.170Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to automate Android release workflows via the Google Play Android Publisher API, including deploying builds, managing listings, and replying to reviews.13MIT
- AlicenseNot gradedqualityDmaintenanceIntegrates Google Play Store management tools with AI assistants to handle app listings, releases, and user reviews. It enables users to manage Play Console tasks like updating store information and retrieving performance statistics through natural language.26 npm10MIT
- AlicenseNot gradedqualityDmaintenanceEnables natural language analysis of Perfetto traces to diagnose Android app performance issues like ANRs, jank, CPU hotspots, memory leaks, and lock contention without writing SQL queries.218Apache 2.0
- FlicenseBqualityBmaintenanceEnables AI agents to manage Google Play apps with scope-based permissions, including publishing internal releases, updating listings, replying to reviews, and promoting to production.1115 npm-
TDQS
Scored across 10 tools
Tools are largely distinct, each targeting a specific aspect of Google Play Vitals (status, releases, errors, anomalies, metrics, versions). The only potential confusion is between play_get_error_reports and play_get_raw_error_reports, but the descriptions clarify different levels of detail (cleaned vs. raw).
All tools follow a consistent 'play_' prefix with snake_case verb_noun patterns (e.g., list_anomalies, compare_versions, get_metric_trends). There are no mixed conventions or ambiguous verbs, making the naming highly predictable.
With 10 tools, the server is well-scoped for its purpose. Each tool adds value—covering discovery, error analysis, metrics, and anomaly detection—without redundancy or overwhelming bloat. The count fits comfortably within the ideal 3-15 range.
The tool set covers the main workflows for monitoring Google Play Vitals: release tracking, error cluster search, detailed reports, ANR summaries, metric trends, and version comparisons. Minor gaps exist (e.g., no dedicated tool for fetching specific version metrics), but agents can work around them using existing tools.