Skip to main content
Glama
Sign In
rabdulsal

playstore-release-mcp

by rabdulsal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to playstore-release-mcp

No user-submitted related servers found.

    Related Servers

    • playstore-cli

      zmij
      A
      license
      Not graded
      quality
      D
      maintenance
      A CLI + bundled MCP server for managing Google Play Console metadata, screenshots, one-time products, and subscriptions from YAML files.
      2 npm
      MIT

    • 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.
      26 npm
      1
      MIT

    • appstore-release-mcp

      rabdulsal
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that drives the full App Store release cycle for iOS and macOS apps: version bump, archive + TestFlight upload, metadata, review submission, and status.
      8
      40 npm
      MIT

    • play-console-mcp

      ilativity
      A
      license
      B
      quality
      B
      maintenance
      Enables managing a Google Play Console app directly from an MCP client: inspecting and shipping releases and staged rollouts, uploading bundles and deobfuscation files, reading Android vitals and anomalies against Google's thresholds, handling reviews and replies, editing store listings and images, managing testers, and checking Digital Asset Links for Trusted Web Activities. Writes are enabled but guarded with dry runs, validate-only edits, and explicit production confirmation.
      41
      1
      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

    A4.1/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource: config verification, track status, bundle upload, releasing, listing text update, graphics upload, review listing, and reply. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    All tools share the 'play_' prefix and most follow a verb_noun pattern (upload_bundle, release_to_track, update_listing, list_reviews, reply_review). 'play_app_status' is a noun phrase rather than a verb action, which is a minor deviation, but the overall pattern is consistent and predictable.

    Tool Count5/5

    8 tools is well-scoped for a Play Store release management server. Each tool covers an essential operation without redundancy, and the count fits comfortably within the typical 3-15 range.

    Completeness4/5

    The surface covers the core release lifecycle (upload, release, status) and store presence (listing text, graphics, reviews). Gaps include inability to read current listing text or images, adjust staged rollout percentages, or manage closed testers, but the primary workflows are sufficiently covered.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources