HarmonyOS MCP service for device automation, app deployment, UI interaction, E2E support, and log validation.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"harmonyos-dev-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# HarmonyOS Dev MCP `harmonyos_dev_mcp` provides HarmonyOS MCP tools for device discovery, app build and deployment, UI automation, E2E inspection, and log validation. [](pyproject.toml) [](https://pypi.org/project/harmonyos-dev-mcp/) [](https://www.python.org/) ## Links - PyPI: [harmonyos-dev-mcp](https://pypi.org/project/harmonyos-dev-mcp/) - Tool reference: [docs/tool_reference.md](docs/tool_reference.md) - Logs query guide: [docs/logs_query.md](docs/logs_query.md) - Release notes: [0.10.0](docs/release_notes_0.10.0.md) ## What It Provides The package exposes 18 MCP tools: ### 0.10.0 highlights - Run all 18 MCP tools directly on HarmonyOS with a pure-Python stdio server, bundled dependency stubs, and direct TCP HDC transport. - Route HDC commands through TCP when `HDC_USE_TCP=1`, including the shell prefix required by the TCP protocol. - Transfer files over TCP in parallel chunks for substantially faster device deployment. - Detect HarmonyOS SDK toolchains and use `HARMONYOS_NODE_PATH` without colliding with the standard Node.js `NODE_PATH` variable. - Verify `input_text` results on composite UI components as well as ordinary text fields. Parameter notation: - `name`: required - `name?`: optional - `name*`: conditionally required, depending on the selected mode or target Device-targeted tools also accept `hdc_server?` for wireless debugging by IP. Pass the wireless HDC endpoint, for example `192.168.43.34:35215`, to route commands as `hdc -t 192.168.43.34:35215 ...`. If both a device SN and an IP endpoint are needed, pass `device_id` as the SN and `hdc_server` as the IP endpoint; commands are routed as `hdc -t <SN> -s <IP:port> ...`. You can also set `HARMONYOS_HDC_SERVER` as a default endpoint. General tools: | Tool | Parameters | |---|---| | `list_devices` | `hdc_…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.