asc-mcp
Related Servers
Alternatives to asc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceLets Claude interact with the App Store Connect API to manage apps, builds, version submissions, sales reports, and Game Center leaderboards and achievements.2117 npmMIT
- AlicenseBqualityDmaintenanceEnables management of App Store Connect operations such as listing apps, managing builds, submitting for review, and handling in-app purchases through Claude Code.2517 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.MIT
- 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
- 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
- AlicenseAqualityAmaintenanceGives Claude Code, Claude Desktop and Cursor access to Apple's full developer API surface — all 1,303 operations — so agents can manage app listings, builds and TestFlight testers, edit metadata and upload screenshots, handle pricing, in-app purchases and subscriptions, reply to customer reviews, and pull sales and finance reports. Includes searchable operation discovery, spec-validated calls, pagination, and read-only, write or full access modes with local key storage.1955 npm1MIT
TDQS
Scored across 7 tools
Each tool targets a distinct App Store Connect resource: apps, builds, beta groups, beta testers, App Store versions and customer reviews. The only near-overlap is get_app vs list_apps, but the singular/plural split and the 'details with latest version state' framing make the boundary clear. Descriptions also spell out optional filters (status, star rating, territory) so parameter choice is unambiguous.
A strict verb_noun pattern holds throughout: get_app plus six list_* tools. Pluralization is used correctly for collections (list_apps, list_builds, list_beta_groups) and singular for the single-resource get. No style mixing.
Seven read-only tools is well-scoped for a focused App Store Connect inspection server, covering apps, builds, TestFlight and reviews without padding. Each tool maps to a distinct listing need; nothing feels redundant or missing at the count level.
The surface is entirely read-only, so there is no lifecycle coverage (no create/update beta group, invite testers, submit/release a version, or respond to reviews), and there is no single-build or single-version detail fetch analogous to get_app. For pure read/inspect workflows the listed resources are reasonably covered, but an agent trying to act on App Store Connect will hit multiple dead ends.