A
licenseNot graded
qualityB
maintenanceMCP server for automating HarmonyOS HAP signing, installation, and verification on devices, enabling natural-language-driven deployment workflows.
72 npm
MIT
devecocli-mcp
by kelai141
Related Servers
Alternatives to devecocli-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server for HarmonyOS development, enabling AI assistants to interact with HarmonyOS projects, devices, and applications.39 npm2MIT
- FlicenseDqualityBmaintenanceEnables HarmonyOS device discovery, app build and deployment, UI automation, E2E inspection, and log validation through MCP tools.1812-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to access unified development tools including code generation, documentation synchronization, test case rendering, and architecture graph queries through a single MCP server.-
- AlicenseBqualityAmaintenanceA comprehensive MCP server for developers providing file operations, shell execution, git integration, and smart caching to enhance AI-assisted development.1114 npmMIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that enables AI agents to inspect projects, generate packaging contracts, build and verify Linux packages, generate multi-platform CI workflows, and orchestrate Windows/macOS/HarmonyOS builds with signing and real install/run validation.44 npmMIT
TDQS
A4.1/5.0
Scored across 9 tools
Disambiguation4/5
Tools are largely distinct by domain: capability_run/list/search, docs_search/read/catalog/tree, skills_find, and status. There is minor overlap between capability_list and capability_search (both discover capabilities) and between docs_catalog and docs_tree (both browse structure), but descriptions clarify their differing intents.
Naming Consistency4/5
Most tools follow a consistent pattern of <domain>_<action> (e.g., capability_run, docs_search). The 'status' tool lacks the pattern (could be environment_status), and skills_find uses a different verb than the capability group, but overall the naming is predictable and readable.
Tool Count5/5
Nine tools is well within the ideal 3-15 range and each serves a distinct purpose in the HarmonyOS development workflow—capability execution, documentation lookup, skill discovery, and environment status. No tool feels redundant or unnecessary.
Completeness5/5
The surface covers the full intended scope: discovering and running capabilities, searching and reading documentation, browsing the doc tree, finding skills, and checking environment readiness. The ability to install skills via capability_run (skills.add) closes the loop, leaving no obvious gaps.
Maintenance
ActivitySlowing
ResponsivenessNo issues