A
licenseA
qualityC
maintenanceLets Claude interact with the App Store Connect API to manage apps, builds, version submissions, sales reports, and Game Center leaderboards and achievements.
21
9 npm
MIT
App Store Connect MCP
by chrischall
Related Servers
Alternatives to App Store Connect MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables management of App Store Connect operations such as listing apps, managing builds, submitting for review, and handling in-app purchases through Claude Code.259 npmMIT
- 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
- AlicenseAqualityCmaintenanceEnables AI assistants to manage Apple App Store Connect resources like apps, builds, TestFlight, and reviews through natural language.2014 npmMIT
- AlicenseBqualityDmaintenanceEnables 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.3193 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
TDQS
A3.7/5.0
Scored across 22 tools
Disambiguation4/5
Most tools target clearly distinct resources and actions (apps, versions, builds, beta testers, reviews, reports, users). The main overlap is get_app_infos vs get_app, whose names and 'list records' vs 'get details' framing could momentarily confuse an agent, but descriptions largely resolve it.
Naming Consistency4/5
Nearly all tools follow a clean verb_noun pattern (list_apps, get_build, invite_beta_tester, remove_testers_from_beta_group, download_sales_report). Minor deviations like get_app_infos (plural noun for a list-style op) and asc_healthcheck break the pattern slightly but remain readable.
Tool Count4/5
22 tools is on the heavier side but justified for a broad domain spanning apps, releases, builds, TestFlight, reviews, financial reports, and team management. Each tool maps to a distinct capability, so nothing feels redundant despite the count.
Completeness4/5
The surface covers read/list/get across apps, versions, builds, testers, reviews, reports, and users, plus key write ops (invite/remove testers, submit build for review, respond to review, invite users). Gaps exist around update/delete for apps, versions, and users, and no app-version submission for App Store review, but core workflows are workable.
Maintenance
ActivityActive
ResponsivenessResponsive