release-guard-mcp
Related Servers
Alternatives to release-guard-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceShips an iOS app to App Store review over the App Store Connect API: a readiness report that says what blocks submission and who can fix it, an idempotent listing pipeline (metadata, screenshots, previews, pricing, age rating, subscriptions), an offline preflight of the app itself, and a guarded submit.4MIT
- AlicenseAqualityAmaintenanceLets coding agents manage apps in App Store Connect through workflow-level tools: shipping TestFlight builds, managing testers and groups, editing listings, replacing and reordering screenshots, handling subscriptions, replying to reviews, downloading sales reports, and submitting for App Review. It is read-only unless writes are explicitly enabled, and destructive actions run as dry runs until confirmed.31MIT
- AlicenseNot gradedqualityBmaintenanceAutomate App Store Connect from your AI agent. Manage versions, metadata, builds, and submissions through natural language.177 npm8MIT
- AlicenseAqualityCmaintenanceAn MCP server that drives the full App Store release cycle for iOS and macOS apps: version bump, archive + TestFlight upload, metadata, review submission, and status.833 npmMIT
- 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
- AlicenseNot gradedqualityDmaintenanceEnables management of iOS/macOS apps, TestFlight builds, app metadata, analytics, and more through natural language interactions with Apple Store Connect API.32 npm49MIT
TDQS
Scored across 6 tools
Tools target distinct concerns: build processing, version lifecycle, readiness, server notifications, text linting, and submission. The only overlap is preflight_submission aggregating build and version checks, but descriptions explicitly route users to the right tool for specific questions.
All tool names use snake_case with a consistent action-first pattern (check_, preflight_, reconcile_, lint_, submit_), making the set predictable and easy to scan.
Six tools is well-scoped for a release-guard server. Each tool earns its place by covering a distinct release-management concern without redundancy or bloat.
The surface covers readiness checks, submission, notification reconciliation, and text linting, with no obvious dead ends for core workflows. Minor gaps exist, such as listing all app versions or editing metadata, but agents can work around them.