io.github.WaterTian/wechat-devtools
wechat_devtools_mcp
Is the io.github.WaterTian/wechat-devtools MCP server down? No. Installed with mcp<2, it started and listed its tools on 2026-11-01.
MCP Server for WeChat DevTools CLI - Automate Mini Program development & testing.
needs mcp<2 probed 2026-11-14 · unchanged since 2026-11-01
A plain install of the package stops at the import below. These tool definitions are from a second install with mcp<2, started in a container with the network off, on 2026-11-01.
MCP error -32000: Connection closed ModuleNotFoundError: No module named 'mcp.server.fastmcp'. This is mcp 2.x, where FastMCP was renamed to MCPServer (from mcp
- Run it
- uvx --with 'mcp<2' wechat-devtools-mcp@0.1.0 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Reports itself as
- wechat_devtools_mcp 1.30.0
- Capabilities
- experimental, prompts, resources, tools
- Repository
- https://github.com/WaterTian/wechat-devtools
- Registry
- active, updated 2026-03-09 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| wechat_get_console_logs | 662 | 6 % |
| wechat_run_automation_script | 551 | 5 % |
| wechat_preview | 437 | 4 % |
| wechat_cloud_func_deploy | 388 | 3 % |
| wechat_navigate_and_capture | 357 | 3 % |
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- Career Kit io.github.W7uuuuz/career-kit · alive
- WAGO PLC io.github.WagoAlex/wago-plc-mcp-server · needs env
- Kingdee K3Cloud (Cloud Galaxy) ERP io.github.WaHaiLong/kingdee-mcp · alive
- io.github.Wangggym/quarry · needs args
- io.github.WaterTian/wechat-devtools-mcp · alive
- io.github.WayforthOfficial/wayforth · needs mcp<2
- io.github.Wchampe/ac-jobs · crashed on start
- io.github.Wchampe/nav-substrate · crashed on start
Servers that mention devtools.
- cn.pianam.mcp/devtools-mcp · alive
- com.clauxel.chromedevtoolsmcp/chromedevtoolsmcp-mcp · no DNS
- Busymate DevTools dev.busymate/busymate-devtools · alive
- dev.workers.marvin-odigo.mcp/krabbot-devtools · alive
- Lead Enrichment API io.github.Compuute/lead-enrichment · alive
- Piranha Vision & DevTools io.github.albermm/piranha-vision · error
- io.github.serkan-ozal/browser-devtools-mcp · needs your URL
- xpay DevTools io.github.xpaysh/devtools · needs your URL
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-01 08:16 | needs mcp<2 | 1.1 s | 42 | 20k | 11k |
| 2026-10-18 06:43 | crashed on start |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The package imports FastMCP from mcp.server.fastmcp. mcp 2.0, the Python SDK of 28 July 2026, renamed FastMCP to MCPServer, and the package asks for mcp with no upper bound, so a plain install (uvx, pip) gets mcp 2.x and the server stops at the import. Installed with mcp<2, it starts and lists its tools. The fix for the publisher: pin mcp<2 in the dependencies, for example mcp>=1.2,<2, and publish a new version, or move to MCPServer as the SDK's migration guide says. Until then, run it with uvx --with 'mcp<2'.
The cause and the fix, with the code before and after: ModuleNotFoundError: No module named 'mcp.server.fastmcp'