appstore-release-mcp
Related Servers
Alternatives to appstore-release-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for shipping iOS apps, enabling screenshots of simulators, managing App Store Connect metadata, and submitting apps for review.17 npmMIT
- AlicenseNot gradedqualityAmaintenanceApp Store Connect MCP server — lets AI agents manage iOS releases, TestFlight builds, screenshots, and review submissions directly from App Store Connect.68 npm1MIT
- AlicenseNot gradedqualityCmaintenanceApp Store Connect MCP Server (Swift) that manages apps, builds, TestFlight, metadata, reviews natively on macOSMIT
- AlicenseBqualityAmaintenanceMCP server for managing Xcode Cloud workflows, builds, and test artifacts via the App Store Connect API.17213 npm1MIT
- AlicenseBqualityFmaintenanceAn MCP server to communicate with the App Store Connect API for iOS Developers25142 npm331MIT
- AlicenseAqualityBmaintenanceLocal-only MCP server for safe App Store Connect access, managing apps, builds, TestFlight, versions, metadata, screenshots, pricing, and review submission, enabling a build to go from uploaded to submitted for review.4439 npmMIT
TDQS
Scored across 8 tools
Each tool addresses a distinct step in the release workflow (environment check, version bump, upload, status polling, build listing, metadata update, submission). No two tools have overlapping responsibilities.
All tools share the 'asc_' prefix and use lowercase with underscores. Most are verb_noun (bump_version, list_builds), but 'asc_doctor' and 'asc_app_status' are noun-based, introducing slight inconsistency.
With 8 tools, the set is well-scoped for a release management server. Each tool serves a necessary function without redundancy, and the number is ideal for agent usability.
The tools cover the essential release lifecycle: environment verification, version bumping, build upload, status tracking, build listing, metadata update, and review submission. Minor gaps like cancellation or rollback are not present but are acceptable for a focused toolset.