Skip to main content
Glama
qalvinahmad

App Store Publisher MCP

by qalvinahmad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to App Store Publisher MCP

No user-submitted related servers found.

    Related Servers

    • play-console-mcp

      OrellBuehler
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to manage Google Play Console reviews and Android app releases, including replying to reviews, promoting releases, managing staged rollouts, and checking crash/ANR vitals.
      44
      20 npm
      1
      MIT

    • dev-publish

      willan23
      F
      license
      B
      quality
      B
      maintenance
      Enables AI agents to manage Google Play apps with scope-based permissions, including publishing internal releases, updating listings, replying to reviews, and promoting to production.
      11
      18 npm
      -

    • aurorarepos-mcp

      KotDath
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to search Aurora OS app store, inspect app and release information, and manage developer applications including RPM upload, metadata editing, and publication scheduling.
      17
      MIT

    • google-cloud-console-mcp

      kutleloove
      A
      license
      B
      quality
      C
      maintenance
      Gives AI assistants hands-on control over Google Play Console and Google Cloud Console using an authorized Google identity. Exposes 95 tools for shipping app builds and release tracks, managing store listings, reviews, in-app products, GCP projects and IAM, Firebase projects and App Distribution, and Cloud Storage or Artifact Registry resources.
      95
      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

    C2.3/5.0

    Scored across 11 tools

    Disambiguation2/5

    Multiple tools are aliases (appgallery_api_request / huawei_api_request, appgallery_get_access_token / huawei_get_access_token), causing ambiguity. Additionally, there are three different token-related tools for Huawei with overlapping purposes, making it hard for an agent to choose the correct one without deep knowledge.

    Naming Consistency2/5

    Naming is inconsistent: tools for AppGallery use 'appgallery_' prefix, but some have 'huawei_' duplicates, and Samsung tools have 'samsung_' prefix. Verb patterns vary (api_request, get_access_token, get_app_details, iap_verify_receipt), lacking a unified structure.

    Tool Count3/5

    11 tools is a moderate count, but the presence of redundant aliases inflates it unnecessarily. The effective count of distinct functionalities is lower, suggesting the set could be streamlined.

    Completeness2/5

    The tools only provide low-level API requests and token management for three app stores. High-level publishing operations like uploading, updating, or submitting apps are missing, leaving significant gaps for a publishing workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources