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.
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.
- 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
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.
One command plus a key — npx @smithery/cli install appstore-connect-mcp-server --client claude, then supply credentials