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

    • 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.
      76
      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.4/5.0

    Scored across 51 tools

    Disambiguation4/5

    Most tools have clearly distinct resource+action targets (list_builds vs get_build, get_screenshot_feedback vs get_crash_feedback, the update_app/update_app_info/update_app_info_localization trio). A few minor overlaps exist, e.g. list_beta_testers is filterable by group while list_group_testers lists a group's testers, and get_build vs get_build_status both surface distribution state, but descriptions give enough signal to pick correctly in most cases.

    Naming Consistency5/5

    Consistent snake_case verb_noun pattern throughout: list_*, get_*, create_*, update_*, download_*, upload_*. Even specialized tools (update_age_rating_declaration, create_analytics_report_request) follow the same convention. No mixing of styles.

    Tool Count2/5

    51 tools is very heavy for a single server, exceeding comfortable agent selection limits. The domain is genuinely broad (TestFlight, App Store versions, analytics, finance, Xcode Cloud, certificates, provisioning), but the sheer count risks selection errors and suggests the surface could be split.

    Completeness4/5

    Very thorough coverage across builds, feedback, analytics, reports, certificates, profiles, Xcode Cloud and App Store metadata, with both read and write operations for listings. Notable gap: no lifecycle management for testers/beta groups (only list operations, no create/invite/remove), which limits end-to-end TestFlight workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources