HuaweiAppGalleryMcp
A Model Context Protocol (MCP) server for managing app publishing on Huawei AppGallery Connect. Integrates directly with Claude Desktop or any MCP-compatible client.
Huawei AppGallery MCP
A Model Context Protocol (MCP) server for managing app publishing on Huawei AppGallery Connect. Integrates directly with Claude Desktop or any MCP-compatible client.
Features
- 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)
- Query AAB compilation status
- Update scheduled release time
- Set GMS dependency flag
- Obtain download/installation and install-failure report URLs
Installation
Via MCP Registry (recommended)
Claude Code:
claude mcp add --from-registry io.github.AgiMaulana/HuaweiAppGalleryMcp
Other MCP clients:
Find it at registry.modelcontextprotocol.io — search for huawei-appgallery.
Manual installation
pip install huawei-app-gallery-mcp
Or with uv:
uv pip install huawei-app-gallery-mcp
Configuration
1. Get API credentials
- Go to AppGallery Connect
- Navigate to Users & Permissions → API key → Connect API
- Click Create and select the App manager role
- Copy the Client ID and Client Secret
These are Connect API credentials — different from HMS Core app credentials.
2. Set environment variables
Create a .env file in your working directory (the server loads it automatically):
HUAWEI_CLIENT_ID=your_connect_api_client_id
HUAWEI_CLIENT_SECRET=your_connect_api_client_secret
# Optional: set a default app ID so you don't have to pass it to every tool call
HUAWEI_APP_ID=your_app_id
3. Connect to your MCP client (manual install only)
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"huawei-appgallery": {
"command": "huawei-app-gallery-mcp",
"env": {
"HUAWEI_CLIENT_ID": "your_client_id",
"HUAWEI_CLIENT_SECRET": "your_client_secret",
"HUAWEI_APP_ID": "your_app_id"
}
}
}
}
Claude Code (machine-level, manual install only)
Create /Library/Application Support/ClaudeCode/managed-mcp.json (macOS) or /etc/claude-code/managed-mcp.json (Linux):
{
"mcpServers": {
"huawei-appgallery": {
"type": "stdio",
"command": "huawei-app-gallery-mcp",
"env": {
"HUAWEI_CLIENT_ID": "your_client_id",
"HUAWEI_CLIENT_SECRET": "your_client_secret",
"HUAWEI_APP_ID": "your_app_id"
}
}
}
}
Tools
All tools accept an optional app_id argument. If omitted, HUAWEI_APP_ID from the environment is used as the default.
| Tool | Description |
|---|---|
query_app_info | Query current app metadata (name, description, category, ratings, etc.) |
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 |
update_release_time | Update the scheduled release time (only when app is in Releasing state) |
set_gms_dependency | Report whether the app depends on GMS |
get_download_report_url | Get download URL for the app download & installation report (CSV/Excel, max 180 days) |
get_install_failure_report_url | Get download URL for the installation failure report (CSV/Excel, max 180 days) |
Usage Examples
Upload and release a new version:
Upload
/path/to/app-release.aab(AAB, file type 5) then submit it for a full release.
Phased rollout:
Submit the app for a phased release to 20% of users.
Open testing:
Submit the app for open testing (channel_id=2).
Update release notes:
Update the English release notes to "Bug fixes and performance improvements".
Scheduled release:
Submit the app for release on March 20, 2026 at 10:00 UTC.
Download report:
Get the download and installation report URL for the last 30 days in English CSV format.
Publishing Workflow
Update app info → Update language info → Upload APK/AAB → Submit app
- Use
update_app_info/update_language_infoto set metadata and release notes - Use
upload_app_fileto upload the binary (handles chunking automatically) - Use
submit_appto trigger review and release
API Reference
This server wraps the AppGallery Connect Publishing API.
License
MIT
관련 서버
SmarterMCP
Business-grade MCP server that emits real operational events and metrics to power decision dashboards, pilots, and automated business systems across any cloud
Remote MCP Server on Cloudflare
A remote MCP server deployable on Cloudflare Workers with OAuth login support.
Okta MCP Server
Allows AI models to interact with your Okta environment to manage and analyze resources, designed for IAM engineers, security teams, and administrators.
CData Salesloft Server
A read-only MCP server by CData that enables LLMs to query live data from Salesloft.
MCP Salesforce Connector
Interact with Salesforce data using SOQL queries and SOSL searches via an MCP server.
Alby MCP Server
Control a Lightning wallet using Nostr Wallet Connect (NWC).
Garmin MCP Server
Connects to Garmin Connect to expose your fitness and health data to MCP-compatible clients.
Dokku
An MCP server for managing applications on Dokku, the open-source PaaS.
Bitrix24
The Bitrix24 MCP Server is designed to connect external systems to Bitrix24. It provides AI agents with standardized access to Bitrix24 features and data via the Model Context Protocol (MCP). The MCP server enables external AI systems to interact with Bitrix24 modules through a single standardized interface. You can connect the Bitrix24 MCP Server to the AI model you already use and manage Bitrix24 directly from it. The MCP server allows actions to be performed and data to be retrieved strictly within the access rights configured in your Bitrix24: the AI agent receives only the information and capabilities that are explicitly requested and authorized. Interaction with the Tasks module is supported (the list of supported modules and available actions is gradually expanding).
Cisco NSO MCP Server
An MCP server for Cisco NSO (Network Services Orchestrator) that exposes NSO data and operations as MCP primitives.