Huawei App Gallery
Related Servers
Alternatives to Huawei App Gallery
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for Apple's App Store Connect API. Manage your iOS, macOS, tvOS, and visionOS apps directly from Claude, Cursor, or any MCP-compatible client.5266 npm23MIT
- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol server that exposes the entire Apple App Store Connect API (1,200+ operations) as MCP tools, enabling AI assistants to query apps, manage builds, handle submissions, read analytics, and more.9 npmMIT
- AlicenseAqualityCmaintenanceA Model Context Protocol (MCP) server that connects Cursor, Claude Desktop, and other MCP clients to the official App Store Connect API—so you can manage iOS/macOS apps, TestFlight, in-app subscriptions, and store metadata via chat or automated tool calls.6983 npm13MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides secure, controlled access to Huawei Cloud services (ECS, OBS, GaussDB, etc.) for AI assistants, enabling cloud resource management through conversational workflows.46Apache 2.0
- FlicenseDqualityDmaintenanceA server built on mcp-framework that enables integration with Claude Desktop through the Model Context Protocol.11-
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for Claude Desktop that connects to 302AI's API services, allowing users to integrate and leverage 302AI capabilities through a structured communication interface.915 npm21MIT
TDQS
Scored across 17 tools
Most tools map to distinct resources and actions, but the upload flow has three overlapping tools (upload_file, upload_app_file, update_app_file_info) and submit_app vs submit_app_with_file are easy to confuse. Descriptions help, but an agent could still pick the wrong step in the upload/release workflow.
Naming follows a clear verb_noun snake_case pattern throughout, using query_, update_, delete_, get_, upload_, and submit_ consistently. Minor inconsistencies like query vs get, change_phased_release_state vs update_phased_release, and upload_file vs upload_app_file prevent a perfect score.
At 17 tools, the set is slightly above the ideal 3-15 range but reasonable for an app publishing console covering metadata, localization, upload, release management, and reports. No tool feels completely redundant, though the set is on the heavier side.
The core release workflow is covered: metadata, localization, upload/attach, submission, phased/scheduled releases, and reports. However, there is no way to query current submission/review/release status, list existing localized listings, or see uploaded files, which creates a notable gap for agents managing the full lifecycle.