Google Play Vitals MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_PLAY_CACHE_TTL | No | Cache duration in seconds (default: 300). | 300 |
| GOOGLE_PLAY_PACKAGE_NAME | No | Default Android application package name (e.g. com.example.app). | |
| GOOGLE_PLAY_CREDENTIALS_JSON | No | Raw JSON string of Service Account credentials (useful for CI/CD or Cloud runtimes). | |
| GOOGLE_APPLICATION_CREDENTIALS | No | Path to Google Cloud Service Account JSON key file. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| play_check_statusC | Verify Google Play API dependencies, GCP Service Account credentials, and environment readiness. |
| play_get_release_tracksA | [Release Discovery] Fetch Google Play release tracks (PRODUCTION, BETA, ALPHA, INTERNAL) and active serving releases with their release names and versionCodes. Essential for automatically discovering the latest production version. |
| play_search_error_issuesB | [Atomic Issue Cluster Search] Search Google Play error clusters (CRASH, ANR, or NON_FATAL) with full AIP-160 filter support. Filter by specific versionCode, user-perceived state, or process state (FOREGROUND/BACKGROUND). Sorted by user impact and occurrences. |
| play_get_error_reportsB | [Atomic Error Reports & Stack Traces] Fetch detailed multi-device sample reports and cleaned de-obfuscated stack traces for a given error issue ID or resource name. |
| play_list_anomaliesA | [Anomaly Detection] List production metric anomalies and sudden regression spikes detected by Google Play algorithms for the application. |
| play_list_accessible_appsB | [Account Apps Discovery] List all Google Play applications accessible by the configured GCP Service Account. |
| play_get_top_anr_summaryA | [One-shot Diagnosis] Retrieve top ANR error clusters along with affected user counts, occurrence rates, and representative cleaned main-thread stack traces. Eliminates back-and-forth round trips. |
| play_get_metric_trendsB | [Token-efficient Metrics] Query trends and daily averages for ANR rate, slow cold start rate (Baseline Profile verification), or Crash rate. Redundant Protobuf metadata is stripped. |
| play_compare_versionsA | [Version Comparison] Compare metrics between two app versions (e.g., before and after Baseline Profile / ANR fixes). Automatically calculates delta and percentage improvement. |
| play_get_raw_error_reportsA | [Deep-dive Drilldown] Fetch multi-device environmental samples and full stack traces for a specific error issue ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-anr-incident | Interactive diagnostic prompt to analyze top production ANR clusters, interpret stack traces, and recommend concrete architectural fixes. |
| verify-baseline-profile | Audit release performance comparing baseline vs. target version to verify Baseline Profile cold-startup acceleration and ANR reductions. |
| vitals-weekly-report | Generate a comprehensive markdown report summarizing weekly Android Vitals trends (ANR rate, crash rate, slow cold start rate). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Google Play Vitals System & Environment Status | Real-time diagnostic overview of dependencies, active package configuration, and GCP credentials. |
TDQS
Scored across 10 tools
Most tools target clearly distinct resources and actions (status, apps, release tracks, anomalies, searches, summaries, trends, version comparisons). The main ambiguity is between play_get_error_reports and play_get_raw_error_reports, which both fetch sample reports and stack traces for an issue ID; the only differentiator is 'cleaned/de-obfuscated' vs 'raw/full', a subtle distinction an agent may miss. Additionally, play_get_top_anr_summary overlaps conceptually with combining play_search_error_issues and play_get_error_reports, though its one-shot purpose is explicitly stated.
Every tool uses the same play_ prefix followed by a consistent verb_noun snake_case pattern (check_status, get_release_tracks, list_anomalies, search_error_issues, etc.). Verb choices (get, list, search, compare, check) are appropriate and predictable for each action type. No deviations in style or casing.
With 10 tools, the server is well-scoped for Google Play Vitals analysis. Each tool covers a meaningful slice of the domain (setup, discovery, error search, detailed reports, summarization, metrics, comparison), so none feel redundant or tacked on. The count sits comfortably in the ideal 3-15 range.
The surface covers the full diagnostic lifecycle: status check, app discovery, release track discovery, anomaly detection, error cluster search, detailed error reports, ANR summary, metric trends, and version comparison. Minor gaps exist, such as no direct tool to fetch a single anomaly's details or a general-purpose metric listing beyond the enumerated ANR/cold-start/crash trends, but these are workaroundable with existing tools.