Huaweiappgallerymcp MCP Server

Most developer tooling work still happens through a UI a human drives. Huaweiappgallerymcp MCP server moves it into the conversation instead. A Model Context Protocol (MCP) server for managing app publishing on Huawei AppGallery Connect. Integrates directly with Claude Desktop or any MCP-compatible client.

The short version

• Query and update app metadata (name, description, category, ratings, support contacts)
• Manage localized store listings per language
• Upload APK / AAB files with automatic chunked upload for large files (>4 GB)
• Submit apps for full release, phased (grey) release, scheduled release, or open testing (channel_id=2)
• Submit apps when the binary is hosted on your own server
• Manage phased release lifecycle (state changes, percentage updates)

The tools it exposes

The server publishes 14 tools. What each one is for:

• query_app_info — Query current app metadata (name, description, category, ratings, etc.), optionally for a specific release channel via channel_id
• update_app_info — Update app metadata in the AppGallery Connect draft
• update_language_info — Add or update a localized store listing for a specific language
• delete_language_info — Remove a localized store listing
• get_upload_url — Obtain a pre-signed upload URL and auth code before uploading a file
• upload_app_file — Upload an APK/AAB from local disk and attach it to the app draft (auto-chunked for >4 GB)
• update_app_file_info — Manually attach already-uploaded files to the app draft
• query_compile_status — Query AAB compilation status for one or more package IDs
• submit_app — Submit the app for review and release (supports full, phased, scheduled, and open testing via channel_id=2)
• submit_app_with_file — Submit when the binary is hosted on your own server
• change_phased_release_state — Change phased release status: proceed, roll back, or stop
• update_phased_release — Convert phased release to full release or update the rollout schedule/percentage

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: HUAWEI_CLIENT_ID, HUAWEI_CLIENT_SECRET, HUAWEI_APP_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Huaweiappgallerymcp's toolset — query_app_info, update_app_info, update_language_info and 11 more — is a fair guide to whether it matches your workflow. It is maintained by agimaulana; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Huaweiappgallerymcp.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.