wechat-devtools-mcp: MCP for WeChat DevTools
wechat-devtools-mcp
An MCP server and skill for WeChat DevTools: an agent compiles, previews, debugs and auto-tests WeChat Mini Programs
- 166 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The agent drives a desktop IDE: it compiles, uploads a project, taps elements and calls page methods
- The server can read project files and evaluate code inside the mini program runtime
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/wechat-devtools-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent drives a desktop IDE: it compiles, uploads a project, taps elements and calls page methods
- The server can read project files and evaluate code inside the mini program runtime
This is third-party code. Review the repository files before installing.
What it does
The server turns WeChat DevTools, the IDE for WeChat Mini Programs, into a toolset for an agent. The author calls the design "thin MCP, fat skill": the server has seven aggregate tools, while procedures and debugging methods live in the paired wechat-devtools skill (nine scenarios, an action reference, staged CDP diagnosis and a troubleshooting guide). Tools are split by task. wechat_ide handles launch and login, wechat_build compiles, previews, uploads and builds npm. wechat_automator taps, types and reads page data and state. wechat_inspector collects console and CDP logs, wechat_screenshot stitches long page screenshots, wechat_navigate goes to a page and collects logs, and wechat_file reads project files. The server runs on Windows and macOS and needs Python 3.10 or newer, Node.js 18 or newer and WeChat DevTools 2.x or 1.06.x. The version at the time of checking is 0.9.21, and the server is listed in the official MCP registry.
Who it is for. Developers of WeChat Mini Programs who want an agent in the editor to build the project, look at pages and find errors on its own.
Good fit when
- A mini program fails to build or crashes in preview and you need console and CDP logs
- You need a full-length page screenshot, for example to compare with a mockup
- Before upload you want to run a standard check: page transitions, page data, state
- An agent must tap elements and set data to reproduce a bug
Not a fit when
- You only need opening a project, compiling and uploading in WeChat DevTools 2.x: the IDE's built-in MCP suits that better
- The project is not a WeChat Mini Program: the server works with them only
- The IDE runs without a graphical session: the server drives the desktop client
Example request
Compile the mini program, open the order list page and show console errors together with a full-page screenshot.MCP
- Transport
- stdio
- Authentication
- not required
Environment variables
WECHAT_DEVTOOLS_CLIrequired- Absolute path to the WeChat DevTools cli.bat or cli.
WECHAT_PROJECT_PATHrequired- Absolute path to the mini program project root.
WECHAT_CDP_PORT- CDP port if 9222 is busy.
Limitations
The server and skill must be installed together at matching versions; check by calling wechat_ide(action='status') and comparing mcp_version with skill_version. The service port must be enabled in WeChat DevTools settings, otherwise opening, compiling and previewing fail with CLI_TIMEOUT. If Chrome holds port 9222, set another through WECHAT_CDP_PORT.
From Stable 2.02.2609240 the IDE's built-in MCP requires its own token, and its config is copied again after the update. This project does not use that interface. Versions up to 0.9.10 are incompatible with mcp SDK 2.0. Most documentation is in Chinese, with a shorter English version.
How to disable. Remove the wechat-devtools-mcp block from the client config and the skill through your client, then optionally run uv tool uninstall wechat-devtools-mcp.
FAQ
How do I check the server is set up correctly?
Call `wechat_ide(action='status')`. The fields `cli_exists`, `project_exists` and `node_available` should be `true`, and `skill_version` should equal `mcp_version`. If not, check both paths in the config and reinstall the skill.
Which clients does it fit?
The README gives configuration for Claude Desktop, Claude Code, Antigravity, Kiro and Trae. The general scheme fits any MCP client that launches commands through uvx.
Must I install the skill together with the server?
Yes, the author requires both. The server exposes only seven aggregate tools, and the procedures and debugging methods live in the skill: `npx -y skills add WaterTian/wechat-devtools-mcp/.agents/skills/wechat-devtools`. For clients such as Trae the skill folder is copied by hand.
How does it differ from the built-in MCP in WeChat DevTools 2.x?
The IDE's built-in server fits opening projects, compiling, uploading and taps better. This project adds stitched long page screenshots, structured CDP logs with history and ready-made check procedures. Version 1.06 has no built-in MCP, and this project works with it.
Does the server work with WeChat DevTools 1.06?
Yes. The 1.06.x builds on NW.js are supported, and they have no built-in MCP. Version 2.x became Stable in August 2026 and ships its own MCP with 49 tools.
Discussion
No questions or reviews yet.
Related
MCP serversMobile Device MCP controls iOS and Android: taps, typing, screenshots and the element tree, with several devices at once
An MCP server that installs on a jailbroken iPhone and gives an agent 46 tools: taps, screenshots, OCR, apps, files and logs
A playbook for AI assistants on WeChat mini programs: from picking a topic and registering to building, monetizing and promoting.
An MCP server to drive iOS and Android: simulators, emulators and real devices via accessibility trees and screenshots
XcodeBuildMCP (now MobileBuildMCP)
XcodeBuildMCP
An MCP server and CLI from Sentry for building, running and testing Xcode iOS and macOS projects from an AI agent
Android MCP Server: control Android through ADB
Android MCP Server
A Python MCP server: the agent takes screenshots of an Android device, reads clickable interface elements and runs ADB commands
README in short
The README opens with a note on how the project relates to the IDE's built-in 2.x MCP, then six install steps, a table of tools and actions and debugging sections. Documentation is in Chinese and in a shorter English version.