A
licenseNot graded
qualityD
maintenanceMCP server for shipping iOS apps, enabling screenshots of simulators, managing App Store Connect metadata, and submitting apps for review.
17 npm
MIT
appstore-connect-mcp
by tomoki013
Related Servers
Alternatives to appstore-connect-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.831 npmMIT
- AlicenseNot gradedqualityAmaintenanceApp Store Connect MCP Server (Swift) that manages apps, builds, TestFlight, metadata, reviews natively on macOSMIT
- AlicenseNot gradedqualityAmaintenanceApp Store Connect MCP server — lets AI agents manage iOS releases, TestFlight builds, screenshots, and review submissions directly from App Store Connect.69 npmMIT
- AlicenseBqualityAmaintenanceMCP server for managing Xcode Cloud workflows, builds, and test artifacts via the App Store Connect API.1618 npm1MIT
- AlicenseNot gradedqualityCmaintenanceLocal MCP server enabling agents to track Xcode Cloud builds and access TestFlight crash reports through the App Store Connect API.19 npmApache 2.0
TDQS
A3.8/5.0
Scored across 44 tools
Disambiguation4/5
Each tool targets a distinct resource and action, with clear descriptions that separate similar-sounding tools (e.g., build status vs upload status vs wait). A few pairs like app-info localization vs metadata could be confused without close reading, but overall the boundaries are well-defined.
Naming Consistency5/5
Every tool follows the consistent pattern asc_<resource>_<action> (e.g., asc_builds_list, asc_version_update, asc_screenshot_upload), using snake_case throughout with no camelCase or irregular verbs. This makes the naming highly predictable and scannable even at scale.
Tool Count2/5
At 44 tools, the server significantly exceeds the 25-tool threshold where coherence typically degrades. While the App Store Connect domain is broad, the granularity here is high and could overwhelm agents; some operations could likely be consolidated.
Completeness4/5
The tool set covers core release workflows comprehensively: app management, builds, versions, metadata, localization, beta groups, pricing, availability, review, screenshots, submission, and preflight. Minor gaps exist—no version deletion, no beta group creation/update, and no privacy management—but they are non-critical for most release automation.
Maintenance
ActivitySlowing
ResponsivenessNo issues