App Store Connect MCP
Related Servers
Alternatives to App Store Connect MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceLets Claude and other AI agents work with Apple's developer API to manage app metadata, versions, review submissions, builds, TestFlight, customer reviews, reports, Xcode Cloud, devices, and team members, with optional read-only safeguards.3685 npmMIT
- AlicenseAqualityAmaintenanceConnects Claude to Apple's App Store Connect API, letting you manage apps, builds, TestFlight beta groups and testers, customer reviews and replies, sales and finance reports, and team users through natural language. Write actions such as invites, beta review submissions, and review responses require confirmation before anything is sent.22179 npm1MIT
- AlicenseBqualityDmaintenanceEnables management of App Store Connect operations such as listing apps, managing builds, submitting for review, and handling in-app purchases through Claude Code.2528 npmMIT
- AlicenseAqualityCmaintenanceLets Claude interact with the App Store Connect API to manage apps, builds, version submissions, sales reports, and Game Center leaderboards and achievements.2128 npmMIT
- AlicenseAqualityBmaintenanceEnables Claude to read and manage App Store listings, builds, TestFlight testers, localized store texts, screenshots, and customer reviews through Apple's official App Store Connect API, with read-only access by default and explicit approval for each change.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage Apple App Store Connect through the official API, including apps, metadata, reviews, TestFlight, provisioning, users, and reports.MIT
TDQS
Scored across 19 tools
Most tools target a distinct resource (apps, builds, beta groups, reviews, localizations, media, settings) and the read/curated set is clearly separated from the generic escape hatch (search_operations -> describe_operation -> call_operation), which is well signposted. Minor overlap remains between asc_fetch_url and asc_call_operation/nextUrl handling, and the three download_*_report tools plus list_analytics_reports vs download_analytics_report could be momentarily confused, though descriptions disambiguate.
All 19 tools use a uniform asc_ prefix with snake_case and a leading verb (list_, download_, search_, describe_, call_, check_, open_, fetch_). The sole nominal name, asc_app_overview, is an intentional one-call aggregate and still reads predictably within the pattern.
19 tools sits at the upper edge of a comfortable set; the curated tools cover the highest-value App Store Connect workflows while search/describe/call_operation collapse the 1,300+ API operations into three tools rather than exploding the surface. It is slightly heavy but each tool has a defensible reason to exist.
Read coverage is strong (apps, builds, versions, localizations, media, reviews, beta groups, sales/finance/analytics reports) and writes/deletes are reachable via asc_call_operation with the access-mode gating explained. The one visible dead end is media: asc_list_media references uploading 'before and after' but no upload tool is offered, and there are no curated create/update helpers for common write flows.