Wechat Dev Mcp

Created By
jiawei6864 months ago
This is a Model Context Protocol (MCP) server that connects to WeChat Developer Tools via miniprogram-automator. It allows you to control the IDE and the mini-program from an MCP client (like Claude Desktop or an AI agent).
Overview

WeChat Developer Tools MCP Server

中文

This is a Model Context Protocol (MCP) server that connects to WeChat Developer Tools via miniprogram-automator. It allows you to control the IDE and the mini-program from an MCP client (like Claude Desktop or an AI agent).

Prerequisites

  1. Node.js: Version 18+ is recommended (though it may work on older versions with some polyfills, this project is set up for modern Node).
  2. WeChat Developer Tools: Must be installed and running.
  3. Enable Automation: In WeChat Developer Tools, go to Settings -> Security Settings and enable Service Port (CLI/HTTP invocation).

Quick Start

Add the following to your claude_desktop_config.json (e.g., ~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "wechat-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "wechat-dev-mcp"
      ]
    }
  }
}

Manual Installation

To install globally:

npm install -g wechat-dev-mcp

Then configure:

{
  "mcpServers": {
    "wechat-devtools": {
      "command": "wechat-dev-mcp",
      "args": []
    }
  }
}

Local Development

  1. Clone the repository
  2. Install dependencies:
    npm install
    
  3. Build and run locally:
    node index.js
    
  4. Configure Claude Desktop to point to your local file:
    {
      "mcpServers": {
        "wechat-devtools": {
          "command": "node",
          "args": ["/absolute/path/to/wechat-dev-mcp/index.js"]
        }
      }
    }
    

Available Tools

  • launch: Launch and connect to a mini-program project.
    • projectPath: Absolute path to the project.
    • cliPath: (Optional) Path to the DevTools CLI.
  • connect: Connect to an already running DevTools instance.
    • wsEndpoint: WebSocket endpoint (e.g., ws://localhost:9420).
  • navigate_to: Navigate to a page (e.g., /pages/index/index).
  • get_page_data: Get data from the current page.
  • set_page_data: Set data on the current page.
  • get_element: Get text, attributes, wxml of an element or tap it.
  • call_method: Call a method on the current page instance.
  • disconnect: Disconnect automation.

Troubleshooting

  • Connection Refused: Ensure WeChat Developer Tools is running and the Service Port is enabled in Settings.
  • Path Issues: Use absolute paths for projectPath.

Server Config

{
  "mcpServers": {
    "wechat-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "wechat-dev-mcp"
      ]
    }
  }
}
Project Info
Created At
4 months ago
Updated At
4 months ago
Author Name
jiawei686
Star
-
Language
-
License
-
Category

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago