Weapp Agent Mcp
Let Claude or Cursor drive WeChat Mini Program debugging and DevTools automation without hand-clicking through the IDE.
Overview
weapp-agent-mcp is a MCP server for the Build phase that automates WeChat Mini Program debugging and WeChat DevTools via an agent-driven connect or launch workflow.
What is this MCP server?
- stdio MCP server @chaixueyuan/weapp-agent-mcp v0.4.7 on npm
- Connect or launch flows via WEAPP_WS_ENDPOINT and WEAPP_AUTOMATOR_MODE
- mp_ensureConnection can auto-start DevTools when a project path is resolved
- WEAPP_PROJECT_PATH, WECHAT_DEVTOOLS_CLI_PATH, and persisted defaults for repeat sessions
- Agent-first automation over WeChat DevTools for debug and routine mini program tasks
- Package version 0.4.7 on npm as @chaixueyuan/weapp-agent-mcp
- stdio transport per MCP server schema 2025-12-11
- Supports explicit launch vs connect via WEAPP_AUTOMATOR_MODE and WEAPP_WS_ENDPOINT
Community signal: 6 GitHub stars.
What problem does it solve?
Debugging mini programs in WeChat DevTools is repetitive and hard to delegate when you are the only developer on the team.
Who is it for?
Indie builders already using WeChat Mini Programs who run Claude Code or Cursor daily and want DevTools steps scripted.
Skip if: Teams building only web or native iOS/Android apps without WeChat, or anyone who cannot install WeChat DevTools locally.
What do I get? / Deliverables
After you register the server, your agent can ensure DevTools connections and run automation against your mini program project from the IDE.
- Registered stdio MCP server for WeChat DevTools workflows
- Configurable launch or connect sessions against a project path
- Agent-callable automation for mini program debug routines
Recommended MCP Servers
Journey fit
How it compares
MCP integration for WeChat DevTools, not a generic browser-testing skill or hosted mini program CI.
Common Questions / FAQ
Who is weapp-agent-mcp for?
Solo and small-team developers shipping WeChat Mini Programs who want their AI coding agent to control WeChat DevTools for debugging and automation.
When should I use weapp-agent-mcp?
Use it during active build and fix cycles when you need repeatable DevTools sessions, connect to an existing automation WebSocket, or auto-launch DevTools against a known project path.
How do I add weapp-agent-mcp to my agent?
Install @chaixueyuan/weapp-agent-mcp, set WEAPP_PROJECT_PATH and optionally WEAPP_WS_ENDPOINT or WECHAT_DEVTOOLS_CLI_PATH, then add a stdio MCP server entry in Claude Code or Cursor pointing at the package.