A
licenseNot graded
qualityB
maintenanceAutomate App Store Connect from your AI agent. Manage versions, metadata, builds, and submissions through natural language.
16 npm
8
MIT
release-guard-mcp
Related Servers
Alternatives to release-guard-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn 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.832 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.81 npm38MIT
- AlicenseAqualityAmaintenanceEnables MCP-capable agents to manage Apple App Store Connect listings by validating repository-based metadata, planning changes, and applying approved updates through Apple's documented APIs.2010 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to diagnose and fix iOS app issues that cause App Store rejections, such as missing privacy manifests, permission strings, and test credentials, before submission.1611 npm2MIT
TDQS
A4.5/5.0
Scored across 6 tools
Disambiguation4/5
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.
Naming Consistency5/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues