Skip to main content
Glama
Sign In
App Store MCP

App Store MCP

by cntechio-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to App Store 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

    • mcp-appstore-connect

      ahmetsina
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage Apple App Store Connect operations including app management, TestFlight, analytics, reviews, subscriptions, and more through 54 tools.
      61
      68 npm
      11
      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 38 tools

    Disambiguation4/5

    Most tools target a distinct resource+action, and the MUTATES/SUBMITS prefixes plus hints like 'poll get_build_upload before assigning the build' clarify sequencing and side effects. A few pairs remain easy to confuse: list_builds vs list_build_uploads, create_localization vs create_app_info_localization, and add_build_to_beta_group vs assign_build_to_version, where the target (beta group vs version) must be read carefully.

    Naming Consistency5/5

    All names use consistent snake_case verb_noun form (list_apps, get_build, create_beta_tester, upload_screenshot, add_tester_to_beta_group, submit_review). Verb choice tracks semantics predictably (list/get for reads, create/update/upload for writes, add_* for membership), so an agent can infer behavior from the name alone.

    Tool Count3/5

    At 38 tools the surface is heavy, sitting well above the comfortable 3-15 range, though this reflects a genuinely large domain (apps, versions, builds, TestFlight, metadata assets, review submission). Each tool maps to a real App Store Connect operation, but the breadth makes discovery and correct selection harder than it needs to be.

    Completeness3/5

    The happy path from upload_ipa through assign_build_to_version to submit_review and release_version is fully covered, including TestFlight and screenshot/localization metadata. However, the surface has no delete or remove operations at all (no delete_screenshot, delete_localization, remove build/tester from a beta group, cancel review submission), and there is no update_app_info for app-level fields like privacy URLs, leaving agents with dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources