Skip to main content
Glama
FidelisMM

shipstores

by FidelisMM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to shipstores

No user-submitted related servers found.

    Related Servers

    • gpc-mcp-server

      muhammetali
      A
      license
      Not graded
      quality
      A
      maintenance
      Google Play Console MCP server — lets AI agents manage releases, track rollouts, reply to reviews, and pull crash/acquisition reports directly from Google Play Console.
      43 npm
      1
      MIT

    • mobile-release-mcp

      Jeronimo0228
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for managing mobile app releases on App Store Connect and Google Play. It exposes 101 tools for iOS and Android release lifecycle and reacts to EAS/GitHub webhooks automatically.
      9 npm
      MIT

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

    A3.5/5.0

    Scored across 60 tools

    Disambiguation4/5

    Tools are mostly distinct with clear prefixes (apple_, play_, eas_, store_) and specific actions, making it easy to select the right one for a given store or task. However, multiple submission-related tools (e.g., eas_submit, apple_submit_for_review, play_submit_for_review) and several 'set_' tools for different metadata fields could cause confusion without careful reading of descriptions.

    Naming Consistency5/5

    Tool names follow a highly consistent pattern: a platform prefix (apple_, play_, eas_, store_) followed by a verb_noun structure (e.g., list_apps, create_version, upload_build). There are no deviations in casing or style, making the set predictable and easy to navigate.

    Tool Count2/5

    With 60 tools, the server far exceeds the typical 3–15 range and even the 25-tool threshold for being overly heavy. While the domain (two app stores plus EAS builds) is broad, the sheer number of tools risks overwhelming an agent and suggests the server could be split into more focused sets.

    Completeness4/5

    The tool surface covers the full lifecycle for both Apple and Google Play: builds, uploads, metadata, submissions, subscriptions, screenshots, and content declarations. Minor gaps exist, such as reading Play reviews or managing Apple in-app purchases beyond subscriptions, but these are not critical for the core publishing workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources