What changed
The wechat-devtools-mcp project has released version 0.9.21, focusing on improving the integration between AI agents and WeChat's Mini Program development environment. A key update addresses how the system handles situations where the CDP (Chrome DevTools Protocol) port, typically port 9222, is already occupied by other applications like Chrome. Previously, this could lead to errors or the agent connecting to the wrong browser instance. The new version introduces a specific CDP_PORT_OCCUPIED error for the open and inspector tools when this occurs, preventing misinterpretation of errors. It also clarifies that the open tool will now directly report this specific error instead of treating it as a startup failure.
Version 0.9.21 also emphasizes the mandatory token requirement for the official built-in MCP server in WeChat DevTools 2.x. Users are reminded to re-copy their MCP configuration from the IDE's security settings after upgrading the official IDE, as this token is necessary for the official tools to function. The project's own MCP server, however, does not rely on this specific interface and is unaffected by this official requirement.
Further refinements include a speed increase for the open tool, which is now approximately four times faster. The call_wx synchronous WeChat API calls are also improved to directly use evaluate without a 10-second timeout. The project continues to support both WeChat DevTools 2.x (Electron-based) and older 1.x versions, with specific handling for Windows 1.x/2.x.
Why it matters for builders
This update is significant for AI builders developing agents or tools that interact with WeChat Mini Programs. The improved CDP port management directly addresses a common point of failure, making agent-driven debugging and inspection more robust. By providing clearer error messages and automatic recovery mechanisms, developers can build more reliable AI assistants for WeChat Mini Program development. The continued focus on compatibility with different DevTools versions ensures broader applicability for these AI tools.
Practical impact
Developers using wechat-devtools-mcp should update to version 0.9.21 to benefit from the enhanced CDP port handling and faster operations. When configuring agents, pay close attention to the WECHAT_DEVTOOLS_CLI and WECHAT_PROJECT_PATH environment variables, ensuring they point to the correct locations for the WeChat DevTools CLI and the project root. For users of WeChat DevTools 2.x, remember to re-authenticate the official MCP server with a new token if prompted by the IDE. The project's documentation provides detailed steps for installation, configuration across various editors (like Claude Desktop, Cursor, VS Code), and skill setup, which are essential for integrating these capabilities into AI workflows.
Caveats and source limits
The source material is a GitHub repository's README file, detailing the release of version 0.9.21. While it provides extensive technical information on installation, configuration, and tool usage, it does not include independent benchmark results comparing performance against previous versions or alternative tools. Specific pricing or licensing details beyond the MIT license are not provided. The release date mentioned in the metadata (2026-11-09) appears to be a future date, which might be an artifact of the data source rather than an actual release date. The excerpt mentions "fresh release" and "4 AI signals, 6 developer signals," but these metrics are not elaborated upon.
Sources
Claim check: 7/7 supported claims - 7 evidence links - 100% avg confidence
- wechat-devtools-mcp has released version 0.9.21.supported - github.com
- Version 0.9.21 improves CDP port occupation handling by introducing a specific `CDP_PORT_OCCUPIED` error for the `open` and `inspector` tools.supported - github.com
- The `open` tool in version 0.9.21 will now directly report CDP port occupation errors.supported - github.com
- The `call_wx` synchronous WeChat API calls are improved to use `evaluate` directly without a 10-second timeout in version 0.9.20.supported - github.com
- The `open` tool is approximately four times faster in version 0.9.17.supported - github.com
- The project requires Python >= 3.10 and Node.js >= 18.supported - github.com
- The project is licensed under the MIT License.supported - github.com
Caveats
- This claim pertains to version 0.9.20, which is a predecessor to the main release of 0.9.21 but is mentioned in the changelog.
- This claim pertains to version 0.9.17, which is a predecessor to the main release of 0.9.21 but is mentioned in the changelog.
- Single-source caution: verify critical details at the linked source.
Radar score 87/100 - how it was calculated
- Reliability 82: GitHub metadata supports source trust
- Freshness 100: Fresh GitHub release date
- Novelty 73: Fresh GitHub release
- Technical 85: Repository technical metadata
- Developer 96: Developer tooling signals
- Ecosystem 72: Fresh GitHub release
- Confidence 96: Claims have reliable evidence
Discussion
Loading comments...