Skip to main content
Glama
getstoreready

getstoreready-mcp

by getstoreready
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to getstoreready-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • 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

    • 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
      32 npm
      11
      MIT

    • Pabal MCP

      quartz-labs-dev
      A
      license
      A
      quality
      D
      maintenance
      Manages App Store Connect and Google Play Console metadata, releases, and ASO workflows locally through MCP tools, enabling store management directly from AI clients without manual console navigation.
      10
      7 npm
      3
      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.5/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct action: Google Play push lifecycle (preview, push, status, link), screen content (images, text, design), store listings (languages, listing text), and auxiliary (credits, translation estimation). No two tools share the same purpose.

    Naming Consistency4/5

    Tools follow a consistent verb_noun snake_case pattern (e.g., push_to_google_play, update_screen_text). Minor inconsistencies: some tools use 'get' vs 'list' (get_google_play_link vs list_store_languages), and 'bulk_update_designs' deviates slightly from the verb_noun structure.

    Tool Count5/5

    15 tools is appropriate for a store management server. Each tool serves a specific function without being overwhelming or insufficient.

    Completeness3/5

    Covers core workflows for Google Play push, screen editing, and listing management. Notable gaps: no App Store push initiation (only status), no actual translation tool (only estimation), and no tool to delete screens or manage screens beyond design/ text.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources