Skip to main content
Glama
App Store Publisher MCP

App Store Publisher MCP

by qalvinahmad

App Store Publisher MCP

MCP server to publish Android apps to Samsung Galaxy Store and Huawei AppGallery straight from AI agents — Claude Code, Claude Desktop, Cursor, VS Code, Google Antigravity, and OpenCode.

Wraps the Samsung Galaxy Store Developer (Seller) API and the Huawei AppGallery Connect API as Model Context Protocol tools, so your AI coding agent can check app status, upload binaries, update store listings, submit apps for review, and verify Samsung IAP receipts — without you ever leaving the editor.

Bonus: docs/app-store-publish-apis.md is a field-tested reference for publishing APIs across 7 stores — Samsung Galaxy Store, Huawei AppGallery, RuStore, Amazon Appstore, vivo, OPPO, and APKPure — including auth flows, endpoints, signing code, and the undocumented gotchas below.

Features

  • 🏪 Samsung Galaxy Store Seller API — app list & details, arbitrary Content Publish API calls (binaries, metadata, submission, staged rollout), JWT service-account auth handled for you

  • 📱 Huawei AppGallery Connect Publishing API — appid lookup, app info, file upload URLs, submission; supports all three Huawei credential types (Connect API client, service-account key JSON, public API key)

  • 🧾 Samsung IAP receipt verification — validate purchase receipt JWTs against your IAP public key

  • 🔐 Tokens cached and auto-refreshed; credentials stay in a local .env, never in code

  • 🤖 Works with any MCP client: Claude Code, Claude Desktop, Cursor, VS Code, Antigravity, OpenCode

Related MCP server: play-console-mcp

Tools

Tool

What it does

samsung_get_access_token

Create/refresh a Seller API access token (JWT RS256 service account)

samsung_get_app_details

GET /seller/contentInfo for a contentId

samsung_api_request

Any Galaxy Store Developer API request (list apps, add binary, submit, …)

samsung_iap_verify_receipt

Verify a Samsung IAP receipt JWT

appgallery_get_access_token / huawei_get_access_token

Connect API client token (the only token type the Publish API accepts)

appgallery_api_request / huawei_api_request

Any AppGallery Connect API request (/api/publish/v2/*)

huawei_get_service_account_token

JWT-bearer token from a service-account key JSON

huawei_sa_api_request

Call Huawei/AGC service APIs with the service-account token

huawei_public_api_request

Call Huawei public APIs with an API key (key= param)

Quick start

git clone https://github.com/qalvinahmad/app-store-publisher-mcp.git
cd app-store-publisher-mcp
npm install
cp .env.example .env   # fill in your credentials

Claude Code

claude mcp add app-store-publisher -- node /path/to/app-store-publisher-mcp/index.js

Claude Desktop / Cursor (mcp.json)

{
  "mcpServers": {
    "app-store-publisher": {
      "command": "node",
      "args": ["/path/to/app-store-publisher-mcp/index.js"]
    }
  }
}

VS Code (~/Library/Application Support/Code/User/mcp.json)

{
  "servers": {
    "app-store-publisher": {
      "type": "stdio",
      "command": "node",
      "args": ["/path/to/app-store-publisher-mcp/index.js"]
    }
  }
}

Google Antigravity (~/.antigravity/mcp_config.json)

{
  "mcpServers": {
    "app-store-publisher": {
      "command": "node",
      "args": ["/path/to/app-store-publisher-mcp/index.js"]
    }
  }
}

OpenCode (~/.config/opencode/opencode.jsonc)

{
  "mcp": {
    "app-store-publisher": {
      "type": "local",
      "command": ["node", "/path/to/app-store-publisher-mcp/index.js"],
      "enabled": true
    }
  }
}

Getting credentials

Samsung Galaxy Store — Seller Portal → Assistance → API Service → create a service account (requires commercial seller status). You get a service-account ID and a private key → SAMSUNG_SERVICE_ACCOUNT_ID, SAMSUNG_PRIVATE_KEY.

Huawei AppGallery — AppGallery Connect → Users and permissions → API key → Connect API → create a client with Project = N/A (team-level; anything else returns 403) → APPGALLERY_CLIENT_ID, APPGALLERY_CLIENT_SECRET. Optionally add a service-account key JSON and/or an API key from Console → Credentials.

Gotchas we learned the hard way (all verified against the live APIs)

  1. Huawei's Publish API only accepts Connect API client tokens. Service-account (JWT-bearer) tokens are rejected with 205524993 "client token auth failed" — no matter which headers you send.

  2. Huawei's client token endpoint wants a JSON body. Sending application/x-www-form-urlencoded fails with an empty error body.

  3. Huawei service-account JWTs must be RS256. PS256 (which the JSON key format suggests) is rejected with sub_error 20504.

  4. Send both headers on Connect API calls: Authorization: Bearer <token> and client_id: <id>.

  5. zod v4 breaks single-argument z.record(). If your MCP server's tools/list dies with Cannot read properties of undefined (reading '_zod'), change z.record(z.any()) to z.record(z.string(), z.any()).

  6. Samsung tokens: the Seller API JWT needs scopes: ["publishing", "gss"] and the access token must be sent together with a service-account-id header.

Security

  • Credentials live only in .env / the service-account JSON — both are gitignored. Use chmod 600 on them.

  • Never put store-publishing credentials in app runtime config; they are deploy-time secrets.

  • If a key leaks (chat, screenshot, log), rotate it in the store console.

Full 7-store publishing API reference (RuStore signature auth, Amazon Appstore edit flow, vivo HMAC signing with working code, OPPO and APKPure manual-only notes): docs/app-store-publish-apis.md

License

MIT © Alvin Ahmad

Available Tools

11 tools
appgallery_api_requestB

Make a request to AppGallery Connect API using the client OAuth token (use this for /api/publish/v2/* endpoints)

Inputs: method (required), endpoint (required), data, params.

appgallery_get_access_tokenA

Generate/refresh AppGallery Connect API access token (client_credentials — required for the Publish API)

Inputs: no named parameters.

huawei_api_requestD

Alias of appgallery_api_request (kept from the old huawei-appgallery-connect MCP)

Inputs: method (required), endpoint (required), data, params.

huawei_get_access_tokenD

Alias of appgallery_get_access_token (kept from the old huawei-appgallery-connect MCP)

Inputs: no named parameters.

huawei_get_service_account_tokenA

Generate/refresh a Huawei service-account token (JWT RS256 jwt-bearer, key file from Console > Credentials > Service account keys). NOT accepted by the Publish API — use appgallery_api_request for publishing.

Inputs: no named parameters.

huawei_public_api_requestC

Make a request to a Huawei public API using the configured API key (sent as the key query parameter)

Inputs: url (required), method (required), data, params.

huawei_sa_api_requestB

Make a request to a Huawei/AGC service API using the service-account Bearer token (for APIs that accept service-account auth; the Publish API does not)

Inputs: url (required), method (required), data, params.

samsung_api_requestC

Make a request to the Samsung Galaxy Store Developer API

Inputs: method (required), endpoint (required), data, params.

samsung_get_access_tokenB

Generate/refresh Samsung Seller API access token

Inputs: no named parameters.

samsung_get_app_detailsC

View Seller's App Details (GET /seller/contentInfo)

Inputs: contentId (required).

samsung_iap_verify_receiptC

Verify Samsung IAP receipt JWT using configured public key

Inputs: receiptJwt (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      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
      60 npm
      2
      MIT
    • F
      license
      B
      quality
      C
      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
      9 npm
      -