harmonyos-dev-mcp
Related Servers
Alternatives to harmonyos-dev-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for automating HarmonyOS HAP signing, installation, and verification on devices, enabling natural-language-driven deployment workflows.72 npmMIT
- AlicenseAqualityBmaintenanceUnified HarmonyOS development MCP server that provides capability search and execution, offline documentation retrieval, and skill marketplace search, enabling AI assistants to manage HarmonyOS projects, build, run, debug, and access official docs via natural language.94 npmMIT
- AlicenseBqualityCmaintenanceEnables mobile device automation on Android and iOS via MCP, including native UI operations, WebView CDP debugging, and reusable JSON flow replay.35Apache 2.0
- FlicenseNot gradedqualityDmaintenanceProvides Android UI automation tools via MCP, enabling device interaction, UI snapshot, and gesture recording.-
- AlicenseBqualityCmaintenanceEnables file operations, npm package management, and configuration checking through MCP.104 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables Docker container management and test execution via MCP tools, supporting image building, container operations, and automated test runs.-
TDQS
Scored across 18 tools
Many tools (e.g., click_element, drag, find_element) lack descriptions, making them indistinguishable. Even with names, similar actions (press_key vs click_element) are ambiguous without documentation.
Naming patterns are mixed: verb_noun (click_element, install_app) appears, but also single words (screenshot, swipe) and object_verb (logs_query). Inconsistent convention hinders predictability.
With 18 tools, the count is slightly above the ideal 3–15 range for a focused server, but still reasonable for UI automation and app lifecycle management. Not excessive.
The tools cover basic CI/CD and UI automation (build, install, uninstall, run, UI interactions, logs). However, missing descriptions and lack of update/debug tools suggest notable gaps in full lifecycle support.