Skip to main content
Glama
devinwang

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to app-store-connect-mcp

No user-submitted related servers found.

    Related Servers

    • appstore-mcp

      forgeopslabs
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that exposes the Apple App Store Connect API to AI agents, enabling management of apps, metadata, in-app purchases, subscriptions, TestFlight, provisioning, reviews, analytics, and more through 113 curated tools plus two generic JSON:API escape-hatch tools.
      2
      -

    • 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

    • App Store Connect MCP

      topcheer
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that exposes the entire Apple App Store Connect API (1,200+ operations) as MCP tools, enabling AI assistants to query apps, manage builds, handle submissions, read analytics, and more.
      6 npm
      MIT

    • mcp-appstore-connect

      ahmetsina
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage Apple App Store Connect operations including app management, TestFlight, analytics, reviews, subscriptions, and more through 54 tools.
      61
      33 npm
      11
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.2/5.0

    Scored across 1316 tools

    Disambiguation2/5

    The set contains hundreds of near-identical pairs such as `*_get_to_one_relationship` vs `*_get_to_one_related` and `*_get_to_many_relationship` vs `*_get_to_many_related`, which an agent will frequently confuse. There is also heavy v1/v2 and deprecated/non-deprecated duplication (e.g. game_center_achievements vs _v2, in_app_purchase_images vs _v2). Names are descriptive but the sheer number of overlapping resource+action variants makes boundaries unclear.

    Naming Consistency4/5

    Tool names follow a highly predictable snake_case pattern of resource_verb_operation (e.g. `app_infos_update_instance`, `subscriptions_delete_instance`), applied uniformly across the whole surface. Minor deviations arise from embedded `_v2`/`_v3` version segments and `[DEPRECATED]` prefixes, but the underlying convention is consistent.

    Tool Count1/5

    1316 tools is an extreme mismatch for any agent workflow; this is a raw 1:1 projection of the entire App Store Connect OpenAPI spec. The volume makes selection impractical and overwhelms the handful of genuinely useful higher-level helpers (asset_upload_file, sales_reports_download, ci_build_run_wait).

    Completeness5/5

    The surface exhaustively covers the App Store Connect domain, including CRUD for apps, builds, subscriptions, in-app purchases, Game Center, CI, reports, and account/auth management. Dedicated helper tools for uploads, report downloads, and polling/waiting further close common workflow gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources