Skip to main content
Glama
Sign In
App Store Connect MCP

App Store Connect MCP

by octopusthink
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to App Store Connect MCP

No user-submitted related servers found.

    Related Servers

    • App Store Connect MCP

      iHux-LLC
      A
      license
      A
      quality
      A
      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
      219 npm
      1
      MIT

    • App Store Connect MCP

      chrischall
      A
      license
      A
      quality
      A
      maintenance
      Connects 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.
      22
      179 npm
      1
      MIT

    • App Store Connect MCP

      jimsimoy
      A
      license
      A
      quality
      C
      maintenance
      Provides AI assistants direct access to Apple's App Store Connect API, enabling them to manage apps, provisioning data, TestFlight builds, and App Store versions, including creating versions, attaching builds, and submitting for review.
      14
      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.5/5.0

    Scored across 36 tools

    Disambiguation4/5

    Most tools target clearly distinct resource+action pairs, and near-neighbor tools (submit_for_review vs submit_build_for_beta_review, list_builds vs list_ci_build_runs, update_version_localization vs update_app_info_localization) are explicitly disambiguated in their descriptions. A few pairs (two localization families, App Store review vs beta review) require reading descriptions rather than being obvious from names alone.

    Naming Consistency4/5

    The dominant pattern is consistent snake_case verb_noun (list_apps, get_build, update_version_localization, register_device, delete_review_response). Minor deviations exist: api_request has no verb, submit_for_review lacks an explicit object, and search_endpoints/describe_endpoint use singular/plural inconsistently, but overall the convention is readable and predictable.

    Tool Count3/5

    36 tools is heavy relative to the typical 3-15 sweet spot, though the App Store Connect domain is genuinely broad (apps, versions, metadata, TestFlight, review, finance, Xcode Cloud, devices) so most tools earn their place. The presence of a generic search/describe/api_request escape hatch suggests the dedicated surface could have been trimmed.

    Completeness4/5

    Coverage spans the full lifecycle: apps, versions, per-locale metadata, builds, TestFlight groups/testers/beta review, App Store review submission, customer reviews, sales and finance reports, devices, bundle IDs, users, and Xcode Cloud. Some gaps (deleting apps/versions, pricing, in-app purchases, user invitations) are covered only via the generic api_request fallback, which agents can work around but must discover.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources