App Store Connect MCP Server
Related Servers
Alternatives to App Store Connect MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables management of iOS/macOS apps, TestFlight builds, app metadata, analytics, and more through natural language interactions with Apple Store Connect API.49 npm37MIT
- AlicenseCqualityCmaintenanceEnables management of App Store Connect resources including app reviews, TestFlight crashes, analytics reports, and Xcode Cloud workflows through natural language or AI agents.401MIT
- AlicenseAqualityCmaintenanceProvides AI assistants direct access to Apple's App Store Connect API, enabling them to manage apps, provisioning data, TestFlight builds, and App Store versions, including creating versions, attaching builds, and submitting for review.14MIT
- 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.3157 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
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Apple App Store Connect operations including app management, TestFlight, analytics, reviews, subscriptions, and more through 54 tools.6132 npm11MIT
TDQS
Scored across 20 tools
Each tool targets a distinct resource and action: apps, builds, versions, beta groups/testers, reviews, users, devices, bundle IDs, certificates, profiles, IAP, subscriptions, and sales. The few related tools (list vs get, list_customer_reviews vs respond_to_review) are clearly differentiated by their verbs and object nouns.
All tool names follow a consistent verb_noun or verb_preposition_noun pattern (e.g., list_apps, get_build, submit_for_review, respond_to_review). Naming is uniformly lowercase with underscores, making the pattern predictable across all 20 tools.
With 20 tools, the set is on the heavier side but still coherent for the broad App Store Connect domain. The count is justified by the many distinct resource types covered, though it approaches the upper limit of what feels manageable.
The tool set is read-heavy, covering listing and getting for most resources, plus a few actions like responding to reviews, submitting for review, and adding beta testers. However, it lacks update/delete operations for apps, builds, versions, users, and other entities, leaving notable gaps in lifecycle management.