Skip to main content
Glama
pofky

asc-mcp

by pofky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to asc-mcp

No user-submitted related servers found.

    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.
      10 npm
      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

      Hiru-ge
      A
      license
      B
      quality
      C
      maintenance
      An unofficial MCP server for the App Store Connect API that enables automation of app management, reviews, TestFlight, analytics, and release processes through natural language.
      63
      46 npm
      2
      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
    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

    A3.5/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools target a distinct resource and action, so an agent can usually tell list_apps from app_details, and attach_build from assign_build_to_group. The main ambiguity is the overloaded word 'review' (customer reviews vs App Review status) and the overlap between list_reviews and triage_reviews, but the descriptions clarify those boundaries.

    Naming Consistency3/5

    The majority of tools follow a readable list_/reate_/et_/upload_ verb_noun pattern, and all names are snake_case. However, a sizable minority are noun phrases such as sales_report, app_details, metadata_diff, and competitor_snapshot, and there are asc_ prefixed helper tools plus set_ vs setup_ verbs, so the naming pattern is mixed rather than fully consistent.

    Tool Count2/5

    41 tools is a very large surface for an MCP server, well beyond the 16-25 band that already feels heavy. Even though App Store Connect is broad, the set could consolidate related operations or reduce browsing load.

    Completeness4/5

    The core App Store submission lifecycle is well covered: metadata, builds, screenshots, preflight, submit, review status, release, phased rollout, plus TestFlight, IAPs, and analytics. Gaps remain around IAP catalog management and beta tester removal, but they are not fatal for the main workflow.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources