StorePilot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STOREPILOT_ASC_KEY_ID | No | Key ID for the App Store Connect API key. | |
| STOREPILOT_ASC_KEY_PATH | No | Path to the App Store Connect API key file (.p8). | |
| STOREPILOT_ASC_ISSUER_ID | No | Issuer ID for the App Store Connect API key. | |
| STOREPILOT_ASC_VENDOR_NUMBER | No | Vendor number for App Store Connect sales reports. | |
| STOREPILOT_GOOGLE_CREDENTIALS | No | Path to the Google Play service account JSON key file. | |
| STOREPILOT_GOOGLE_REPORTS_BUCKET | No | Name of the Cloud Storage bucket for Play reports (e.g., pubsite_prod_rev_0123456789). |
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 | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| setup_doctorA | Diagnose StorePilot's store credentials and report exactly what is missing. Runs every setup step independently and reports all of them, so a single failure never hides the rest. For Google Play it verifies: the service account key parses (and shows the email you must grant access to), the Android Publisher API is reachable, the Play Developer Reporting API is reachable and lists your apps, the "Reply to reviews" permission is present (the API returns an empty list rather than an error when it is missing), and the Cloud Storage reports bucket is configured and readable. Each failing step comes with the exact fix. Run this first whenever a Play tool returns empty or unexpected data. |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly defined and distinct.
The single tool name 'setup_doctor' is descriptive and uses snake_case. With only one tool, there are no conflicting naming conventions to create inconsistency.
The server has only one tool, which is too few for a service called StorePilot. The name implies broader functionality like managing reviews, but only a diagnostic helper is provided.
The tool only diagnoses credentials and does not provide any actual store management operations. It references 'Play tools' that are absent, leaving the surface severely incomplete.