wechat-devtools-mcp
Related Servers
Alternatives to wechat-devtools-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to drive the WeChat DevTools CLI and HBuilderX CLI directly, so they can open mini-program projects, compile uni-app sources, generate preview QR code images, upload trial builds, and run static audits on page completeness, bundle size, and appid. It requires no SDK dependencies and leaves projects and IDEs untouched, simply wrapping their built-in command lines behind a standard stdio MCP interface.MIT
- -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 AI agents to control WeChat DevTools on Windows through the official CLI and mini program automation SDK, supporting project operations, simulator navigation, element interaction, screenshots, evaluation, and wx API calls.23MIT
- AlicenseBqualityDmaintenanceEnables 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
- 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
- AlicenseNot gradedqualityDmaintenanceConnects WeChat Mini Program tooling to MCP and automation workflows. Provides scripts for opening, previewing, and uploading projects, as well as automator smoke tests.1MIT
TDQS
Scored across 7 tools
The tools are mostly distinct by domain: IDE lifecycle, build/upload, automation, logging, navigation, file reading, and screenshots each have a clear role. There is some overlap between wechat_inspector and wechat_navigate because both collect CDP logs, and wechat_navigate depends on wechat_automator being started, but the descriptions make the intended boundaries reasonably clear.
All tools use a consistent wechat_ prefix and snake_case style, which makes the set predictable. The suffixes are mostly domain nouns (ide, build, automator, inspector, file) with one verb-like name (navigate), a minor deviation from an otherwise stable pattern.
Seven tools is well-scoped for a WeChat DevTools MCP server. Each tool represents a meaningful capability group with sub-actions, avoiding both a fragmented one-action-per-tool surface and an oversized tool list.
The surface covers the main developer workflow: IDE lifecycle, project/file inspection, build/preview/upload, screenshots, automation, navigation, and log collection. Minor gaps exist, such as no explicit automator stop/teardown action and no targeted element screenshot, but core workflows are well covered.