Skip to main content
Glama
swlittles

App Store Connect MCP

by swlittles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to App Store Connect MCP

No user-submitted related servers found.

    Related Servers

    • asc-mcp

      anupamchugh
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to manage App Store Connect apps, including registering bundle IDs, uploading metadata and screenshots, setting age ratings, managing TestFlight groups and testers, and submitting apps for review.
      MIT

    • 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

    • release-guard-mcp

      InovaPlatforms
      A
      license
      A
      quality
      C
      maintenance
      Enables a coding agent to answer "is this iOS release ready?" by running read-only App Store Connect checks: build processing, App Review state, a 13-point submission preflight, release-notes policy linting, and App Store Server Notification reconciliation. The lone write capability is a dry-run-first, seven-gate submission tool that always requires explicit confirmation.
      6
      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.8/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action (builds vs screenshots vs testers vs reviews vs subscriptions), and the destructive/write tools are well-differentiated. Minor overlap exists between set_whats_new and update_listing (which also sets what's new), and asc_request is a deliberate catch-all that could tempt use where a workflow tool fits better.

    Naming Consistency5/5

    Every tool is snake_case with a verb-first pattern (list_*, get_*, create_*, update_*, remove_*, upload_*, etc.), matching resource nouns consistently. asc_request is the only mild deviation but is still readable and intentional.

    Tool Count3/5

    31 tools is on the heavy side and exceeds the comfortable 3-15 range, though the App Store Connect domain is genuinely broad (builds, testers, screenshots, listings, subscriptions, reviews, reports, review submission). The surface is large but mostly earns its place rather than being redundant.

    Completeness4/5

    Strong lifecycle coverage: app discovery, build upload/distribution, TestFlight groups and testers, listing/metadata editing, screenshots, age rating, subscriptions/offers, reviews, and review submission. Known gaps (pricing/availability, App Privacy questionnaire, paid intro offers) are explicitly documented and bridged by the asc_request escape hatch.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources