App Store Publisher MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUAWEI_API_KEY | No | Huawei public API key (optional) | |
| SAMSUNG_PRIVATE_KEY | No | Samsung private key | |
| APPGALLERY_CLIENT_ID | No | Huawei AppGallery Connect API client ID | |
| APPGALLERY_CLIENT_SECRET | No | Huawei AppGallery Connect API client secret | |
| HUAWEI_SERVICE_ACCOUNT_KEY | No | Huawei service-account key JSON (optional) | |
| SAMSUNG_SERVICE_ACCOUNT_ID | No | Samsung service account ID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| samsung_get_access_tokenB | Generate/refresh Samsung Seller API access token |
| samsung_get_app_detailsC | View Seller's App Details (GET /seller/contentInfo) |
| samsung_api_requestC | Make a request to the Samsung Galaxy Store Developer API |
| samsung_iap_verify_receiptC | Verify Samsung IAP receipt JWT using configured public key |
| appgallery_get_access_tokenA | Generate/refresh AppGallery Connect API access token (client_credentials — required for the Publish API) |
| huawei_get_access_tokenD | Alias of appgallery_get_access_token (kept from the old huawei-appgallery-connect MCP) |
| appgallery_api_requestB | Make a request to AppGallery Connect API using the client OAuth token (use this for /api/publish/v2/* endpoints) |
| huawei_api_requestD | Alias of appgallery_api_request (kept from the old huawei-appgallery-connect MCP) |
| 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. |
| 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) |
| huawei_public_api_requestC | Make a request to a Huawei public API using the configured API key (sent as the |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
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 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.
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.
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.