Skip to main content
Glama
Sign In
App Store Connect MCP

App Store Connect MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to App Store Connect MCP

No user-submitted related servers found.

    Related Servers

    • app-store-connect

      RayanBayat
      A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      3
      MIT

    • App Store Connect MCP

      octopusthink
      A
      license
      A
      quality
      C
      maintenance
      Lets 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.
      36
      85 npm
      MIT

    • App Store Connect MCP

      iHux-LLC
      A
      license
      A
      quality
      B
      maintenance
      Gives 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.
      19
      55 npm
      1
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.7/5.0

    Scored across 22 tools

    Disambiguation4/5

    Nearly every tool pairs a distinct resource with a distinct action (reviews vs. builds vs. testers vs. users vs. reports), and the descriptions draw clear lines between close pairs like delete_beta_tester (team removal) and remove_testers_from_beta_group (group membership only). The only soft spot is the app-metadata family — get_app, get_app_infos, list_app_store_versions, list_apps — where an agent must know App Store Connect's data model to pick correctly.

    Naming Consistency4/5

    Strong, predictable snake_case verb_noun pattern: list_*, get_*, invite_*, delete_*, add_/remove_*, download_*, submit_*, respond_to_*. Minor deviations: asc_healthcheck breaks the verb-first pattern and carries an odd namespace prefix, and get_app_infos uses a singular 'get' verb with a plural noun.

    Tool Count4/5

    22 tools is on the heavy side, but the App Store Connect domain genuinely spans apps, reviews, builds, TestFlight testers/groups, team users, and financial reports, so each tool maps to a real area. A few tester/group operations could arguably be consolidated (e.g. tester invite vs. add-to-group), but nothing feels redundant filler.

    Completeness3/5

    Core read paths and the highest-value writes (beta tester lifecycle, review responses, build submission for beta review, report downloads) are covered, with a useful healthcheck tool for diagnosing failures. Notable gaps remain: no create/delete for beta groups, no way to create or edit App Store versions or submit them for App Review, no app info/metadata updates, and no coverage of in-app purchases or pricing — all common App Store Connect workflows.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources