Upload App MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPPLY_JSON_KEY | No | Full path to the Google Play publishing key, set in the ~/.config/google-play-console/.env file. Takes priority over GOOGLE_APPLICATION_CREDENTIALS. | |
| PLAY_CONSOLE_ENV_FILE | No | Path to an alternative env file for the Google Play credentials (defaults to ~/.config/google-play-console/.env). | |
| APP_STORE_CONNECT_KEY_ID | No | App Store Connect API key ID, e.g. 2X9R4HXF34. Required for App Store Connect (iOS) tools. | |
| APP_STORE_CONNECT_ENV_FILE | No | Path to an alternative env file for the App Store Connect credentials (defaults to ~/.config/app-store-connect/.env). | |
| APP_STORE_CONNECT_ISSUER_ID | No | App Store Connect API issuer ID, e.g. 57246542-96fe-1a63-e053-0824d011072a. Required for App Store Connect (iOS) tools. | |
| GOOGLE_APPLICATION_CREDENTIALS | No | Full path to the Google Play service account JSON key (from Google Cloud with the Google Play Android Developer API enabled). Required to publish to Google Play. | |
| APP_STORE_CONNECT_PRIVATE_KEY_PATH | No | Full path to the App Store Connect .p8 private key file. Required for App Store Connect (iOS) tools. |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| upload_androidB | Upload an .aab to a Google Play test track: internal, alpha, beta or the name of a custom closed track. |
| promote_androidA | Promote a version code from a Google Play test track to production. A rollout below 1 starts a staged rollout. release_notes sets the release notes in the given Play language code. Without confirm=true it only validates with Google Play and publishes nothing. |
| update_rollout_androidA | Change a Google Play production release: a new rollout fraction, 1 to complete it, or halt=true to stop it. Without confirm=true it only validates with Google Play and publishes nothing. |
| status_androidB | List the Google Play releases of every track with version codes, status and rollout fraction. |
| upload_iosC | Upload an .ipa to TestFlight without waiting for Apple's processing. |
| release_iosA | Attach a TestFlight build to an App Store version, creating the version if needed, and submit it for review. release_notes sets What's New in every language of the live version. Without confirm=true it only describes what it would do. |
| status_iosB | Show the latest App Store versions with their state and the latest builds with their processing state. A build can be submitted only after it is VALID. |
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 7 tools
Each tool maps to a distinct platform and lifecycle action: iOS status/upload/release versus Android upload/promote/rollout-update/status. The closest overlap, promote_android and update_rollout_android, is clarified by one promoting to production and the other modifying an existing production rollout.
All names use snake_case with a clear action plus platform suffix pattern (status_ios, upload_android, promote_android, release_ios, etc.). The convention is predictable across both platforms.
Seven tools is well-scoped for a mobile app upload/release server. Each tool covers a meaningful lifecycle operation without redundant variants.
The surface covers core upload, status, promotion, rollout, and review-submission workflows for both iOS and Android. Minor gaps remain, such as Android build-processing status and iOS review cancellation, but the main lifecycle is covered.