mcp-appstore-reviews
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APP_STORE_CONNECT_KEY_ID | Yes | Key ID of the API key | |
| APP_STORE_CONNECT_ISSUER_ID | Yes | Issuer ID shown at the top of the Integrations page | |
| APP_STORE_CONNECT_PRIVATE_KEY_PATH | Yes | Path to the downloaded .p8 private 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_reviewsA | List customer reviews for an app, newest first by default. Each review includes its id, star rating, title, body, reviewer nickname, territory, date, and the existing developer response (with its id) if one exists. Use the response id with delete_review_response. |
| respond_to_reviewA | Publish a public developer response to a customer review. One response per review — if the review already has a response, delete it first with delete_review_response, then respond again. |
| delete_review_responseA | Delete an existing developer response. Takes the response id (the response.id field surfaced by list_reviews), not the review id. |
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 3 tools
Each tool has a clear, distinct purpose: listing reviews, responding to a review, and deleting a response. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (list_reviews, respond_to_review, delete_review_response).
Three tools cover the essential operations for app store review responses: list, respond, and delete. The count is well-scoped for this domain.
Covers the full lifecycle of review responses (read, create, delete). Minor gap: no direct update for a response (requires delete+create), but the documentation clarifies the intended workflow.