TestFlight Feedback MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASC_KEY_ID | No | The Key ID from App Store Connect (found in Users and Access > Keys) | |
| ASC_PASSWORD | No | Apple ID password (required if ENABLE_BROWSER_AUTH is true) | |
| ASC_USERNAME | No | Apple ID email address (required if ENABLE_BROWSER_AUTH is true) | |
| ASC_ISSUER_ID | No | The Issuer ID from App Store Connect (found in Users and Access > Keys) | |
| ASC_PRIVATE_KEY | No | The inline content of your App Store Connect .p8 private key | |
| ENABLE_BROWSER_AUTH | No | Set to true to enable browser-based authentication for retrieving full text feedback (requires Playwright) | |
| ASC_PRIVATE_KEY_PATH | No | The file path to your App Store Connect .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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_appsB | List all apps in your App Store Connect account. Returns app ID, name, bundle ID, and SKU. |
| list_buildsA | List TestFlight builds for an app. Filter by version or processing state. Returns build number, version, upload date, and status. |
| list_beta_testersA | List beta testers. Filter by app, group, or email. Returns tester name, email, invite type, and state. |
| list_beta_groupsB | List beta tester groups for an app. Returns group name, internal/external status, and feedback settings. |
| list_feedbackA | List TestFlight feedback for an app. Retrieves screenshot submissions, crash reports, and (with browser auth) text comments. Filter by build or feedback type. |
| get_feedback_detailA | Get detailed information about a specific feedback submission, including device info, tester details, screenshot asset, or crash log reference. |
| get_crash_logA | Download the crash log content for a specific beta feedback crash submission. |
| respond_to_feedbackA | Send an email to a beta tester letting them know their feedback has been addressed. Looks up the tester's email from the submission and sends via SMTP. |
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 8 tools
Each tool targets a distinct resource or action (apps, groups, testers, builds, feedback, crash logs, and responses). Even the two feedback-related tools have clear separation: list_feedback retrieves items, get_feedback_detail provides in-depth detail, and get_crash_log downloads specific crash content.
All tool names follow a consistent verb_noun pattern using lowercase with underscores (e.g., list_apps, get_feedback_detail, respond_to_feedback). This makes the set predictable for an agent to learn and select tools.
8 tools is well-scoped for a TestFlight feedback MCP. Each tool serves a necessary function without redundancy, covering the essential workflows: listing resources, retrieving details, downloading crash logs, and responding to feedback.
The tool set covers the core TestFlight feedback lifecycle: listing apps/groups/testers/builds/feedback, retrieving detailed info and crash logs, and responding. Minor gaps exist, such as the ability to delete feedback or manage beta tester invitations, but these are not critical for the stated purpose.