
Harmonyos
io.github.FadingLight9291117Published by GitHub account FadingLight9291117v1.0.3Updated Oct 24, 2026
MCP server for HarmonyOS development - interact with projects, devices, and applications
Overview
A local MCP server for HarmonyOS development that lets an assistant query connected devices, project configuration, build outputs and installed apps.
- What you can do
- List connected HarmonyOS devices and read details such as model, manufacturer and OS version for a given device ID. Read project metadata from app.json5 and list a project's modules with their HAP/HSP/HAR types. Check whether build outputs exist and list the generated HAP and HSP files. List installed applications on a device and show details such as version, install time and whether an app is a system app.
- When to use it
- Useful when working on HarmonyOS projects and you want an assistant to inspect devices, project structure, build artifacts and installed apps without running hdc commands by hand. The README positions it for quick read-only queries, with building and deploying left to shell commands.
- Requirements
- Node.js 18 or later, installed locally via npm or npx. HarmonyOS DevEco Studio must be installed and its hdc command-line tool available on the PATH. A HarmonyOS device connected over USB with Developer Options and USB debugging enabled for device and app queries.
Installation
In SourceWeft
- Open Harmonyos in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
MCP HarmonyOS
npm: https://www.npmjs.com/package/mcp-harmonyos
[NPM Version] [GitHub Stars] [License]
A Model Context Protocol (MCP) server for HarmonyOS development. This server enables AI assistants like Claude to interact with HarmonyOS projects, devices, and applications.
Features
- Device Management: List and query connected HarmonyOS devices
- Project Information: Read project configuration, modules, and build outputs
- Application Management: List and inspect installed applications on devices
- Build Verification: Check build outputs and project structure
Prerequisites
- Node.js 18+
- HarmonyOS DevEco Studio (for hdc command-line tools)
hdcmust be available in your PATH
Installation
Global Installation (Recommended)
Or use with npx
Configuration
For OpenCode
Add to your ~/.config/opencode/opencode.json:
For Claude Desktop
Add to your Claude Desktop configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Available Tools
Device Management
harmonyos_list_devices
List all connected HarmonyOS devices.
Returns: Array of devices with UDID and status
harmonyos_get_device_info
Get detailed information about a specific device.
Parameters:
deviceId(string): The device UDID
Returns: Device information including model, manufacturer, OS version, etc.
Project Information
harmonyos_get_project_info
Get HarmonyOS project information from app.json5.
Parameters:
projectPath(string): Absolute path to the HarmonyOS project root
Returns: Project metadata including bundleName, version, and modules
harmonyos_list_modules
List all modules in a project with their types (HAP/HSP/HAR).
Parameters:
projectPath(string): Absolute path to the HarmonyOS project root
Returns: Array of modules with name, type, and path
harmonyos_check_build_outputs
Check if build outputs exist and list them.
Parameters:
projectPath(string): Absolute path to the HarmonyOS project root
Returns: Build output information
Application Management
harmonyos_list_installed_apps
List all installed applications on a device.
Parameters:
deviceId(string): The device UDID
Returns: Array of installed applications
harmonyos_get_app_info
Get detailed information about an installed application.
Parameters:
deviceId(string): The device UDIDbundleName(string): The application bundle name
Returns: Detailed application information
Usage Examples
With OpenCode
After configuring the MCP server, you can ask OpenCode questions like:
OpenCode will use the MCP tools to query information and can combine them with bash commands for building and deploying:
Design Philosophy
This MCP server follows the "lightweight query + external operations" pattern:
- MCP tools provide fast, structured queries (device info, project metadata, app status)
- Bash commands handle long-running operations (building, deploying)
- AI assistants intelligently combine both for complete workflows
This design ensures:
- ✅ Fast response times (all queries < 1 second)
- ✅ No timeout issues with long builds
- ✅ Clear error messages and logs
- ✅ Easy to maintain and extend
Development
Build from Source
Project Structure
Troubleshooting
"hdc command not found"
Make sure DevEco Studio is installed and hdc is in your PATH:
"No devices connected"
- Enable Developer Options on your device (tap Build Number 7 times)
- Enable USB Debugging
- Connect device via USB
- Run
hdc list targetsto verify connection
"app.json5 not found"
Make sure you provide the absolute path to the project root directory (where AppScope/app.json5 is located).
License
MIT
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Related Resources
Source: README.md at commit 72f0e79
Tools
0Version history
1- v1.0.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts