Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

by erayendes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Heimdall App Store Connect MCP

Related Servers

  • asc-mcp

    zelentsov-dev
    A
    license
    Not graded
    quality
    A
    maintenance
    MCP server for App Store Connect API with 208 tools across 25 workers. Manage apps, builds, TestFlight, in-app purchases, subscriptions, reviews, provisioning, screenshots, analytics, and more — directly from Claude, Cursor, VS Code, or any MCP client. Multi-account support, worker filtering, JWT auth.
    69
    MIT

  • App Store Connect MCP

    topcheer
    A
    license
    Not graded
    quality
    B
    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.
    9 npm
    MIT

  • App Store Connect MCP

    beautyfree
    A
    license
    A
    quality
    C
    maintenance
    A Model Context Protocol (MCP) server that connects Cursor, Claude Desktop, and other MCP clients to the official App Store Connect API—so you can manage iOS/macOS apps, TestFlight, in-app subscriptions, and store metadata via chat or automated tool calls.
    69
    83 npm
    13
    MIT

  • 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
    -

  • asc-mcp

    pofky
    A
    license
    A
    quality
    A
    maintenance
    An opinionated MCP server for App Store Connect that provides 13 curated tools, slash-command workflows, and a Claude Skill to manage apps, reviews, sales, and pre-submission audits via natural language.
    41
    72 npm
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3/5.0

Scored across 353 tools

Disambiguation2/5

Most CRUD tools are distinct on the surface, but dozens of high-level workflow tools deliberately duplicate raw endpoint chains (e.g. release__submit vs review_submissions__create), and many relationship tools carry opaque suffixes that make it hard to tell read vs write or parent vs child at a glance. The descriptions help, but the sheer size of the set makes boundaries unclear.

Naming Consistency2/5

Raw tools mostly follow a resource__action schema, but the pattern is not uniform: verbs are sometimes the last segment (__get, __list, __create) and sometimes embedded (__build__set, __search_keywords__add), while high-level tools use unrelated prefixes like listing__, pricing__, and asc__. Collision-avoidance suffixes such as _0zdb21 and _1vi3gd add further inconsistency.

Tool Count1/5

353 tools is far beyond a practical agent-facing surface and makes selection itself a major failure point. Many low-level relationship getters and high-level summary tools could be consolidated into a much smaller, intentional set.

Completeness4/5

The server covers an unusually broad slice of App Store Connect: apps, builds, beta, review submission, pricing, localizations, analytics, sales, and more. A few gaps remain, such as no explicit update tool for customer review responses and some resources exposed only as relationships, but agents can generally find a viable path through the domain.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources