Skip to main content
Glama
OrellBuehler

testflight-mcp

by OrellBuehler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to testflight-mcp

No user-submitted related servers found.

    Related Servers

    • asc-feedback-mcp

      max-rousseau
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes App Store Connect TestFlight beta feedback including screenshot submissions, crash submissions, crash logs, and screenshot downloads as tools for MCP-capable clients.
      2
      BSD 3-Clause

    • 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.
      9 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

      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
    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

    B3.4/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools target a distinct resource and action, and the list/get/download patterns are explicit. However, a few pairs overlap meaningfully: get_build and get_build_status both return TestFlight distribution state, and list_beta_testers vs list_group_testers both enumerate testers, so an agent could occasionally misselect.

    Naming Consistency5/5

    Every tool follows a consistent snake_case verb_noun convention (list_, get_, create_, download_) with predictable resource suffixes. There are no mixed naming styles or vague verbs.

    Tool Count2/5

    41 tools is far above the typical well-scoped range and will strain an agent's tool-selection context. Although the server spans several distinct Apple APIs, the count is still excessive and many adjacent read tools could be consolidated.

    Completeness3/5

    The read surface is extensive across TestFlight, App Store, Xcode Cloud, analytics, finance and device assets, but the server is almost entirely query-only. There are notable gaps in lifecycle operations such as updating/deleting testers, groups, localizations or versions, and submitting releases for review.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources