Skip to main content
Glama
erayendes

Heimdall App Store Connect MCP

Related Servers

Alternatives to Heimdall App Store Connect MCP

Related Servers

  • 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.
    82
    MIT
  • 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.
    16 npm
    1
    MIT
  • A
    license
    A
    quality
    D
    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
    76 npm
    14
    MIT
  • F
    license
    Not graded
    quality
    C
    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
    -
  • 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
    117 npm
    1
    MIT

TDQS

B3.2/5.0

Scored across 376 tools

Disambiguation3/5

Most tools map 1:1 to distinct App Store Connect endpoints, but there is heavy overlap between high-level wrappers (pricing__set_subscription_price, release__submit, listing__upload_screenshot, analytics__get_report) and the raw endpoint tools that do the same work, plus inverse-direction relationship pairs (builds__beta_groups__add vs beta_groups__builds__add vs beta_testers__beta_groups__add) that force arbitrary choice. Descriptions do an unusually good job of saying 'use this instead of chaining X', and asc__search_tools helps discovery, which keeps it from being worse.

Naming Consistency3/5

The dominant pattern is domain__resource__action with double-underscore separators and consistent get/list/create/update/delete verbs, which is readable. But it breaks down repeatedly: many relationship tools have machine-truncated names with random suffixes (app_store_version_experiments_v2__app_store_version_exper_0b7r4g, app_store_version_localizations__pla_1gpxt4), and curated wrappers switch to verb-first naming (listing__upload_asset, pricing__make_offer, preflight__check_version, reviews_ai__triage), mixing two conventions in one surface.

Tool Count1/5

376 tools is an extreme mismatch for what an agent can reasonably navigate, even for a large domain like App Store Connect. The 1:1 endpoint mirroring floods the surface with dozens of trivially related list/get tools and near-duplicate wrappers, so any single task requires searching through hundreds of options.

Completeness5/5

Coverage is essentially exhaustive: full CRUD across apps, versions, localizations, builds, TestFlight, in-app purchases, subscriptions, pricing, experiments, App Clips, review submissions, plus finance/sales/analytics reports and App Store Server API (StoreKit) operations. Curated preflight, release, pricing and analytics wrappers close the common multi-step workflow gaps that raw endpoints leave open.

Maintenance

ActivityActive
ResponsivenessWithin a week