Developer · Local MCP server
Weapp Agent MCP
Agent-first MCP server for WeChat Mini Program debugging & automation via WeChat DevTools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Chaixueyuan/weapp-agent-mcp- Version
- 0.4.8
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-01
- Updated
- 2026-07-01
- Publisher
- Chaixueyuan (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Chaixueyuan) · how
- Repository
- github.com/Chaixueyuan/weapp-agent-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @chaixueyuan/weapp-agent-mcp | 0.4.8 | stdio |
How to connect Weapp Agent MCP
Weapp Agent MCP runs locally from a Node.js package published to the npm registry: @chaixueyuan/weapp-agent-mcp version 0.4.8. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @chaixueyuan/weapp-agent-mcp@0.4.8. It reads these environment variables: WEAPP_WS_ENDPOINT, WEAPP_AUTOMATOR_MODE, WEAPP_PROJECT_PATH, WECHAT_DEVTOOLS_CLI_PATH, WEAPP_DEVTOOLS_PORT, WEAPP_DEVTOOLS_TIMEOUT, WEAPP_AUTO_ACCOUNT (secret), WEAPP_DEVTOOLS_TICKET (secret), WEAPP_TRUST_PROJECT, WEAPP_DEVTOOLS_ARGS, WEAPP_DEVTOOLS_CWD, WEAPP_AUTOCLOSE, WEAPP_AUTOLAUNCH, WEAPP_LAUNCH_TIMEOUT and WEAPP_CONNECT_TIMEOUT; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"weapp-agent-mcp": {
"command": "npx",
"args": [
"-y",
"@chaixueyuan/weapp-agent-mcp@0.4.8"
],
"env": {
"WEAPP_WS_ENDPOINT": "<value>",
"WEAPP_AUTOMATOR_MODE": "<value>",
"WEAPP_PROJECT_PATH": "<value>",
"WECHAT_DEVTOOLS_CLI_PATH": "<value>",
"WEAPP_DEVTOOLS_PORT": "<value>",
"WEAPP_DEVTOOLS_TIMEOUT": "<value>",
"WEAPP_AUTO_ACCOUNT": "<secret>",
"WEAPP_DEVTOOLS_TICKET": "<secret>",
"WEAPP_TRUST_PROJECT": "<value>",
"WEAPP_DEVTOOLS_ARGS": "<value>",
"WEAPP_DEVTOOLS_CWD": "<value>",
"WEAPP_AUTOCLOSE": "<value>",
"WEAPP_AUTOLAUNCH": "<value>",
"WEAPP_LAUNCH_TIMEOUT": "<value>",
"WEAPP_CONNECT_TIMEOUT": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Wcag AccessibilityA WCAG accessibility testing MCP for AI agents, Codex, Claude Code, and automated UI audits. | Local · stdio |
| Wcag22 Css LintReads your stylesheet and names the success criterion each rule breaks, including the three WCAG 2.2. | Local · stdio |
| WeakspotAudit Solidity and Rust contracts from your editor. Pays per audit in USDC over x402. | Local · stdio |
| WealthSchemaCited 2026 U.S. planning figures (IRS, SSA, CMS), synthetic household samples, and an AI benchmark. | Remote · HTTPLive check: ✓ handshake |
| WeavatrixNative Weavatrix MCP: 67 read-only tools for code, local CI, n8n, Dify, agents, Mermaid, Web3. | Local · stdio |
| Weavatrix GitFast, bounded, read-only Git evidence for local AI coding agents. | Local · stdio |
| Weavatrix JsAlways-fresh local repo graph: LSP-backed impact, Health, dead code, endpoints, architecture. | Local · stdio |
| Weavatrix RefactorTransactional refactoring extension with 11 evidence-backed tools, previews, and rollback. | Local · stdio |