Release Health MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RELEASE_HEALTH_CONFIG | No | Path to the config.yaml file used to configure backend, apps and read key file (e.g. passed as RELEASE_HEALTH_CONFIG=/path/to/config.yaml) | |
| RELEASE_HEALTH_BACKEND | No | Environment override for the backend setting in config.yaml (e.g. fixture or play) | |
| RELEASE_HEALTH_READ_KEY | No | Environment override for the path to the read-only Google Play service account JSON key file | |
| RELEASE_HEALTH_THRESHOLDS | No | Environment override for the path to the thresholds.yaml file |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Release health for Android apps on Google Play. Use these tools to decide whether a staged
rollout is healthy enough to expand. Typical flow: list_releases → recommend_rollout; drill into
get_release_health, top_crashes or new_issues to explain the decision. All tools are read-only:
this server never changes a rollout. app accepts a configured alias or a package name; omit
version_code to use the release currently rolling out on production. Rates are fractions
(0.0109 = 1.09% of users).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_releasesB | Current releases on a Play track with status and staged-rollout fraction. |
| get_release_healthB | Crash and ANR rates for a version, compared with the previous version that has data. |
| top_crashesB | Largest crash/ANR issues in a version by affected users, with a sample stack trace. |
| new_issuesA | Crash/ANR issues first seen in this version (likely regressions). |
| recommend_rolloutA | Recommend expand, hold or halt for a staged rollout, with reasons, using thresholds.yaml. This is advice only; it does not change the rollout. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The tools mostly target distinct questions: listing releases, health metrics, top crashes, new regressions, and rollout advice. The only mild overlap is between top_crashes and new_issues, since both surface crash/ANR issues, but their ranking and regression framing help distinguish them.
Three tools follow a clear verb_noun pattern: recommend_rollout, list_releases, and get_release_health. top_crashes and new_issues do not use the same imperative-verb convention, making the set readable but not fully consistent.
Five tools is well-scoped for a release-health advisory server. Each tool covers a meaningful part of the workflow without excessive surface area.
The set covers release listing, health metrics, top issues, new regressions, and rollout recommendation, which is strong coverage for an advisory release-health domain. Minor gaps may exist around deeper release/track detail or historical trends, but core workflows are supported.