WeChat DevTools MCP
Related Servers
Alternatives to WeChat DevTools MCP
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceEnables AI agents to debug and control WeChat Mini Programs through WeChat DevTools, including direct automator operations and CLI-backed features like screenshots, logs, previews, and uploads.-
- AlicenseAqualityBmaintenanceEnables Claude, Codex, and other AI agents to run end-to-end tests against WeChat Mini Programs by launching WeChat DevTools, querying and acting on elements, navigating pages, mocking wx APIs, capturing screenshots, reading console logs, and making assertions with failure evidence.131MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to control WeChat mini-programs running in WeChat Developer Tools through MCP tools. Provides automation capabilities for launching, navigating, querying, and interacting with pages and elements.611MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to automate WeChat Developer Tools for mini programs, allowing navigation, inspection, and manipulation of pages and components through the miniprogram-automator API.27136 npm174MIT
- AlicenseAqualityAmaintenanceWraps the WeChat DevTools CLI as an MCP service, enabling AI in editors to call WeChat CLI commands for mini-program development, testing, debugging, and automation.7167MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to automate WeChat mini-programs via launch or connect modes, providing a stable interaction tree for observation and operation.MIT
TDQS
Scored across 23 tools
Most tools have clearly distinct purposes (build, login, preview, upload, navigate, screenshot, etc.), and the descriptions disambiguate overlapping pairs like wdt_open vs wdt_auto_start vs wdt_auto_connect and wdt_close_project vs wdt_quit vs wdt_disconnect. The remaining fuzziness is in the runtime-evaluation cluster: wdt_evaluate, wdt_wx_method, and wdt_page_data all execute things inside the mini program, and wdt_element is a mega-tool with ~20 actions that could be mistaken for wdt_page_data or wdt_native depending on the task.
Every tool uses the same wdt_ prefix with snake_case descriptive names (wdt_build_npm, wdt_current_page, wdt_system_info), with no camelCase or style drift. The verb/noun ordering is predictable and readable throughout.
23 tools is on the high side, but the surface splits into two real layers (official CLI control and automation-socket interaction), and nearly every tool maps to a distinct operation with no obvious filler. It is slightly heavy — a few tools like wdt_auto_connect/wdt_disconnect could be folded in — but not bloated.
Coverage of the domain is strong: project lifecycle, login/preview/upload, automation connect/disconnect, page navigation, element interaction, data access, screenshots, wx method calls, and waiting are all present. Notable gaps are console/log retrieval and network request interception/mocking, plus richer storage or performance tooling, which agents would need workarounds for.