A
licenseA
qualityC
maintenanceEnables AI assistants to manage Apple App Store Connect resources like apps, builds, TestFlight, and reviews through natural language.
20
7 npm
MIT
io.github.gjeltep/app-store-connect-mcp
by gjeltep
Related Servers
Alternatives to io.github.gjeltep/app-store-connect-mcp
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
- 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.3155 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
- 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
- FlicenseNot gradedqualityDmaintenanceEnables management of App Store Connect apps including registration, listing, IPA upload, store listing updates, and in-app purchase creation via natural language.-
TDQS
C2.9/5.0
Scored across 40 tools
Disambiguation4/5
Each tool targets a distinct resource and action within its category. The analytics tools follow a clear hierarchy (requests -> reports -> instances -> segments) that is discernible from descriptions, though the naming could be clearer. No two tools appear to do exactly the same thing.
Naming Consistency3/5
Most tools follow a resource_action pattern, but analytics tools mix conventions: e.g., 'reports_list_instances' vs 'analytics_report_requests_list' vs 'report_requests_get'. Nested list tools use a different word order than top-level lists, and 'builds_start_by_ref_id' is an outlier. Still, names are generally readable and predictable within categories.
Tool Count2/5
40 tools is well above the 25+ threshold for heavy tool sets. While they cover a broad API, many are simple list/get variations, and an agent would be overwhelmed. Some consolidation (e.g., combining list and search, or using parameters for different resource hierarchies) could reduce the count.
Completeness2/5
The server covers analytics, reviews, crash reports, user management, and Xcode Cloud, but omits major App Store Connect areas like app metadata, TestFlight builds/beta groups, certificates, devices, and in-app purchases. Within included domains, coverage is fairly thorough, but the overall surface is incomplete for a server claiming to be an App Store Connect MCP.
Maintenance
ActivityInactive
ResponsivenessNo issues