add_tester_to_group
Add a new tester to a beta group
LABSCO SUMMARY
Tester feedback arrives as something you can act on, not a link to open.
Beta feedback comes back with the screenshot image itself plus the device model, OS version and tester comment, so a report can be read and triaged in the turn it is found rather than in a browser afterwards. Around it sits the paperwork half of a release — versions, localizations edited a field at a time, bundle IDs and capabilities, and the report pipeline that ends in a downloadable segment. One tool points the other way: list_schemes reads an Xcode project on your disk rather than anything in App Store Connect.
What it is
An App Store Connect client covering TestFlight groups and feedback, App Store versions and localizations, bundle IDs and capabilities, devices, users, and the analytics, sales and finance report downloads.
What you get
- Beta feedback submissions listed with their screenshots, device information and tester comments, filterable by build, device model, OS version or tester — and a single submission returned with the image downloaded
- TestFlight roster management: beta groups listed, their testers listed, a tester added by email and name, a tester removed
- Release preparation: an App Store version created against a build with copyright, release type and earliest release date, its localizations listed, and one localization field updated at a time
- Identifier setup: a bundle ID registered, a capability enabled or disabled on it, registered devices and team users listed
- Analytics as data, not dashboards: a report request created, its reports and segments listed, and a segment downloaded from its URL
- Sales and finance reports downloaded by date, frequency, report type and region code
- Schemes read out of a local Xcode project or workspace
Requirements
An App Store Connect API key: APP_STORE_CONNECT_KEY_ID, APP_STORE_CONNECT_ISSUER_ID, and the .p8 private key file on disk at APP_STORE_CONNECT_P8_PATH. Sales and finance downloads additionally need the vendor number in APP_STORE_CONNECT_VENDOR_NUMBER.
Setup effort
Add the configuration to your client
USE CASES
01
Triaging a TestFlight bug report
List the feedback for a build, narrowing by device model or OS version when the report sounds device-specific, then open the submission itself to get the screenshot and the tester's comment.
02
Opening a build to a new group of testers
Find the group, add the tester by email and name, and read the roster back to confirm they landed in the right one rather than the internal group next to it.
03
Preparing the next release listing
Create the version against the build with its release type and earliest release date, then walk its localizations and update them a field at a time — which is also how you fix one locale without touching the rest.
04
Registering a new app's identifiers
Register the bundle ID, switch on the capabilities the app needs, and list what the team already has so you find the existing identifier before creating a near-duplicate.
05
Pulling last month's numbers
Sales and trends come back by date and frequency; finance reports come back per region. Both need the vendor number, which is why it sits in the environment rather than in every call.
06
Getting app analytics out as data
Analytics arrives as a request that yields reports, reports that yield segments, and segments that carry download URLs. Four calls, and the numbers are yours to work with rather than to read off a dashboard.
27 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_analytics_report_request
Create a new analytics report request for an app
create_app_store_version
Create a new app store version for an app
create_bundle_id
Register a new bundle ID for app development
disable_bundle_capability
Disable a capability for a bundle ID
download_analytics_report_segment
Download data from an analytics report segment URL
download_finance_report
Download finance reports for a specific region
download_sales_report
Download sales and trends reports
enable_bundle_capability
Enable a capability for a bundle ID
get_app_info
Get detailed information about a specific app
get_app_store_version_localization
Get detailed information about a specific app store version localization
get_beta_feedback_screenshot
Get detailed information about a specific beta feedback screenshot submission. By default, downloads and returns the screenshot image.
get_bundle_id_info
Get detailed information about a specific bundle ID
list_analytics_report_segments
Get segments for a specific analytics report (contains download URLs)
list_analytics_reports
Get available analytics reports for a specific report request
list_app_store_version_localizations
Get all localizations for a specific app store version
list_app_store_versions
Get all app store versions for a specific app
list_apps
Get a list of all apps in App Store Connect
list_beta_feedback_screenshots
List all beta feedback screenshot submissions for an app. This includes feedback with screenshots, device information, and tester comments. You can identify the app using either appId or bundleId.
list_beta_groups
Get a list of all beta groups (internal and external)
list_bundle_ids
Find and list bundle IDs that are registered to your team
list_devices
Get a list of all devices registered to your team
list_group_testers
Get a list of all testers in a specific beta group
list_schemes
List all available schemes in an Xcode project or workspace
list_users
Get a list of all users registered on your App Store Connect team
remove_tester_from_group
Remove a tester from a beta group
update_app_store_version_localization
Update a specific field in an app store version localization
BEFORE YOU INSTALL
What to know first
Tools you get
27 tools when we connected. download_sales_report and download_finance_report register only when APP_STORE_CONNECT_VENDOR_NUMBER is set; with just the three required credentials you get 25. Install it as appstore-connect-mcp-server, as the config blocks do; the scoped name in the README's manual-install line is not on npm.
Requires
- npx on PATH
- APP_STORE_CONNECT_KEY_ID in your environment
- APP_STORE_CONNECT_ISSUER_ID in your environment
- APP_STORE_CONNECT_P8_PATH in your environment
CONTEXT COST
Moderate Standing cost
Rated by the size of the 27 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"app-store-connect": {
"command": "npx",
"args": [
"-y",
"appstore-connect-mcp-server"
],
"env": {
"APP_STORE_CONNECT_KEY_ID": "<YOUR_APP_STORE_CONNECT_KEY_ID>",
"APP_STORE_CONNECT_ISSUER_ID": "<YOUR_APP_STORE_CONNECT_ISSUER_ID>",
"APP_STORE_CONNECT_P8_PATH": "<YOUR_APP_STORE_CONNECT_P8_PATH>",
"APP_STORE_CONNECT_VENDOR_NUMBER": "<YOUR_APP_STORE_CONNECT_VENDOR_NUMBER>"
}
}
}
}Cursor
Install link: https://cursor.com/install-mcp?name=app-store-connect&config=JTdCJTIyY29tbWFuZCUyMiUzQSUyMm5weCUyMC15JTIwYXBwc3RvcmUtY29ubmVjdC1tY3Atc2VydmVyJTIyJTdE
