App Store Connect MCP
Related Servers
Alternatives to App Store Connect MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceLets Claude interact with the App Store Connect API to manage apps, builds, version submissions, sales reports, and Game Center leaderboards and achievements.2125 npmMIT
- AlicenseBqualityCmaintenanceEnables management of App Store Connect operations such as listing apps, managing builds, submitting for review, and handling in-app purchases through Claude Code.2525 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables management of iOS/macOS apps, TestFlight builds, app metadata, analytics, and more through natural language interactions with Apple Store Connect API.81 npm38MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to manage Apple App Store Connect resources like apps, builds, TestFlight, and reviews through natural language.2015 npmMIT
- AlicenseBqualityCmaintenanceEnables interaction with Apple's App Store Connect API through natural language to manage apps, beta testing, localizations, analytics, sales reports, and CI/CD workflows for iOS and macOS development.31104 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage Apple App Store Connect through the official API, including apps, metadata, reviews, TestFlight, provisioning, users, and reports.MIT
TDQS
Scored across 22 tools
Most tools target clearly distinct resources and actions (apps, builds, TestFlight testers, reviews, reports, users). Minor potential confusion exists within the TestFlight cluster (invite_beta_tester vs add_testers_to_beta_group, delete_beta_tester vs remove_testers_from_beta_group) and get_app vs get_app_infos, but the descriptions clarify the boundaries.
Overwhelmingly consistent verb_noun snake_case (list_apps, get_build, invite_user, download_sales_report). The only deviations are get_app_infos (unusual plural) and asc_healthcheck (different prefix/single-word), but both remain readable and predictable.
22 tools is on the higher side, but the server spans several genuinely separate subdomains (apps, builds, TestFlight, reviews, sales/finance, team users), so most tools map to a distinct resource. Still slightly heavy rather than tightly scoped.
Solid read/write coverage for TestFlight, reviews, reports, and users. However, core App Store Connect lifecycle operations are missing: no App Store version create/update/submit-for-review (release management), no app info updates, and no user role updates or removal, which are notable gaps for the stated domain.