SuperAPI AI Directory

HuaweiAppGalleryMcp

Huawei AppGallery Connect publishing: upload APK/AAB, update metadata and localizations, submit for review, and manage phased rollouts.

Open website

About this tool

HuaweiAppGalleryMcp is a Model Context Protocol (MCP) server for managing app releases on Huawei AppGallery Connect. It can be integrated directly with Claude Desktop or any MCP-compatible client.

Main capabilities

  • Query and update app metadata: name, description, category, rating, support contact information.
  • Manage localized store information per language.
  • Upload APK / AAB files; large files (over 4 GB) are automatically uploaded in chunks.
  • Submit apps for the following release methods: full release, phased (staged) release, scheduled release, open testing (channel_id=2).
  • Submit apps when the binary file is hosted on your own server.
  • Manage the phased release lifecycle (status changes, percentage updates).
  • Query AAB compilation status.
  • Update scheduled release time.
  • Set the GMS dependency flag.
  • Get download/install and installation failure report URLs.

Installation methods

Via MCP Registry (recommended)

Other MCP clients: search for huawei-appgallery on registry.modelcontextprotocol.io to find it.

Manual installation

  1. Obtain 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 the working directory (the server will load it automatically).
  3. Connect the MCP client (only for manual installation):
    • macOS: add to ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: add to %APPDATA%\Claude\Claude_desktop_config.json
    • Or create /Library/Application Support/ClaudeCode/managed-mcp.json (macOS) or /etc/claude-code/managed-mcp.json (Linux)

All tools accept an optional app_id parameter. If omitted, HUAWEI_APP_ID from the environment variables is used as the default.

Usage examples

  • Upload and release a new version: upload /path/to/app-release.aab (AAB, file type 5), then submit for full release.
  • Phased release: submit the app for a phased release to 20% of users.
  • Open testing: submit the app for open testing (channel_id=2).
  • Check open testing: use query_app_info(channel_id=2) to query the app metadata for the open testing channel.
  • Update release notes: update the English release notes to "Bug fixes and performance improvements".
  • Scheduled release: submit the app to be released on March 20, 2026 at 10:00 UTC.
  • Download reports: get the download and installation report URLs for the past 30 days in English CSV format.

Release workflow

  1. Use update_app_info / update_language_info to set metadata and release notes.
  2. Use upload_app_file to upload the binary file (chunking is handled automatically).
  3. Use submit_app to trigger review and release.

Packaging release workflow

For packaging release instructions, see docs/RELEASE.md.

This server wraps the AppGallery Connect Publishing API.