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.
    76
    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.
    24 npm
    MIT

  • App Store Connect MCP

    beautyfree
    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
    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
    132 npm
    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

B3.1/5.0

Scored across 354 tools

Disambiguation2/5

Many tools overlap in purpose: high-level convenience tools (e.g., pricing__get_subscription_price, listing__get_screenshots) explicitly replace chains of low-level tools, yet both remain available. Auto-generated relationship names with truncated suffixes (e.g., app_clip_default_experiences__release_with_app_store_vers_0zdb21) are opaque and hard to distinguish. With 354 tools, misselection is likely.

Naming Consistency4/5

Tool names overwhelmingly follow a consistent snake_case pattern with double-underscore separators and the action as the final segment (list, get, create, update, delete). The few auto-generated hash suffixes (e.g., _0az88b) and domain-specific prefixes (pricing__, listing__) are minor deviations that don't break predictability.

Tool Count1/5

354 tools is far beyond any reasonable threshold for an MCP server, even for a complex API like App Store Connect. While the server attempts mitigation via domain loading and search tools, the surface remains overwhelming and impractical for an agent to navigate reliably.

Completeness4/5

The surface covers a vast majority of App Store Connect resources with full CRUD where the API allows, plus high-level workflows for pricing, listings, releases, and metadata. Some gaps exist (e.g., no app price schedule update, limited app custom product page creation), but these are minor and often constrained by Apple's API.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources