query_app_infoLABSCO SUMMARY
Phased rollout is where this stops being a convenience.
Uploading a binary from a chat is nice; being able to say 'stop the rollout' and have it happen immediately is the reason to wire this in. Proceeding, rolling back, halting and changing the percentage are each their own call, so the release can be steered from wherever you notice the problem — including from a phone.
What it is
A server over AppGallery Connect's publishing API. It covers the release cycle end to end — metadata, localised listings, binary upload, submission and phased release — with the app id defaulted from the environment so most calls do not need it.
What you get
- query_app_info and update_app_info for the draft's metadata, name, description, category and support contacts
- update_language_info and delete_language_info for a store listing in one language
- get_upload_url and upload_app_file — an APK or AAB from disk, chunked automatically when it is very large
- update_app_file_info to attach a binary you uploaded some other way
- query_compile_status for where an AAB is in compilation
- submit_app for review and release — full, phased, scheduled, or open testing
- submit_app_with_file when the binary is hosted on your own server
- change_phased_release_state and update_phased_release to proceed, roll back, stop, or change the rollout percentage
- update_release_time and set_gms_dependency
- get_download_report_url and get_install_failure_report_url for the reports after release
Requirements
Connect API credentials — HUAWEI_CLIENT_ID and HUAWEI_CLIENT_SECRET, created under Users & Permissions with the App manager role. These are not the same as HMS Core app credentials, which is the usual first mistake. Set HUAWEI_APP_ID to avoid passing the app to every call. Installed with pip, as the package huawei-app-gallery-mcp.
Setup effort
One command plus credentials — pip install huawei-app-gallery-mcp, then supply credentials
USE CASES
01
Getting a new build in front of reviewers
Upload the binary, attach it to the draft, and submit for review.
02
Fixing the store listing before release
Read the current metadata and update the description or the localised listing for one language.
03
Rolling out gradually and stopping if it goes wrong
Submit as a phased release, raise the percentage as it holds, and roll back the moment it does not.
04
Waiting on a build that is still compiling
Poll the compilation status rather than resubmitting.
05
Timing a release for a specific moment
Set the scheduled release time instead of watching the clock.
06
Finding out how the release is landing
Fetch the download and install-failure report URLs after it is live.
16 tools
Listed in project docs. Your client may show a different list.
update_app_infoupdate_language_infodelete_language_infoget_upload_urlupload_app_fileupdate_app_file_infoquery_compile_statussubmit_appsubmit_app_with_filechange_phased_release_stateupdate_phased_releaseupdate_release_timeset_gms_dependencyget_download_report_urlget_install_failure_report_urlBEFORE YOU INSTALL
What to know first
Tools you get
16 tools named in the project's documentation.
Requires
- huawei-app-gallery-mcp on PATH
- HUAWEI_CLIENT_ID in your environment
- HUAWEI_CLIENT_SECRET in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
pip install huawei-app-gallery-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"huawei-appgallery": {
"command": "huawei-app-gallery-mcp",
"env": {
"HUAWEI_CLIENT_ID": "<YOUR_HUAWEI_CLIENT_ID>",
"HUAWEI_CLIENT_SECRET": "<YOUR_HUAWEI_CLIENT_SECRET>",
"HUAWEI_APP_ID": "<YOUR_HUAWEI_APP_ID>"
}
}
}
}Claude Code — manual
CLAUDE CODE — MANUAL · JSON
{
"mcpServers": {
"huawei-appgallery": {
"type": "stdio",
"command": "huawei-app-gallery-mcp",
"env": {
"HUAWEI_CLIENT_ID": "<YOUR_HUAWEI_CLIENT_ID>",
"HUAWEI_CLIENT_SECRET": "<YOUR_HUAWEI_CLIENT_SECRET>",
"HUAWEI_APP_ID": "<YOUR_HUAWEI_APP_ID>"
}
}
}
}
