App Store Connect MCP
Related Servers
Alternatives to App Store Connect MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage Apple App Store Connect through the official API, including apps, metadata, reviews, TestFlight, provisioning, users, and reports.MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to manage App Store Connect apps, including registering bundle IDs, uploading metadata and screenshots, setting age ratings, managing TestFlight groups and testers, and submitting apps for review.MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to manage Apple App Store Connect resources like apps, builds, TestFlight, and reviews through natural language.2015 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Apple App Store Connect operations including app management, TestFlight, analytics, reviews, subscriptions, and more through 54 tools.6142 npm11MIT
- 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 gradedqualityDmaintenanceEnables management of iOS/macOS apps, TestFlight builds, app metadata, analytics, and more through natural language interactions with Apple Store Connect API.43 npm37MIT
TDQS
Scored across 14 tools
Each tool targets a distinct resource and action: apps (list/get/find), versions (create/list/get/attach/submit), TestFlight builds/beta groups/testers (list only), and account resources (bundle IDs, certificates, profiles). Even though list_apps, get_app, and find_app_by_bundle_id all retrieve app info, their input methods differ clearly, preventing misselection.
All tool names follow the same verb_noun pattern in snake_case (create_, list_, get_, find_, attach_, submit_). The only minor deviation is 'find_app_by_bundle_id' which uses 'find' instead of 'get', but it remains consistent in structure and readability.
14 tools is well-scoped for an App Store Connect server covering app management, TestFlight builds, version lifecycle, and submission. Each tool addresses a specific workflow step without unnecessary overlap, making the count appropriate for the domain.
The server covers the core workflow of listing apps, fetching versions, attaching builds, and submitting for review, but lacks critical CRUD operations: there is no create/update/delete for apps, no ability to manage beta testers beyond listing, and no way to create or edit beta groups. These gaps would require agent workarounds or external calls.