Wechat Devtools

io.github.WaterTianPublished by GitHub account WaterTianv0.1.0Updated Oct 24, 2026

MCP Server for WeChat DevTools CLI - Automate Mini Program development & testing.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Local MCP server that drives the WeChat DevTools CLI so an assistant can automate Mini Program development and testing.

What you can do
  • Automate WeChat Mini Program development and testing through the WeChat DevTools command-line interface.
  • Run CLI commands against a default Mini Program project path, with a configurable command timeout.
  • Point the server at a specific DevTools CLI and Node.js executable via environment variables.
When to use it
Useful when you develop or test WeChat Mini Programs on a desktop machine with WeChat DevTools installed and want an assistant to run DevTools CLI operations instead of switching to the GUI.
Requirements
Runs locally as a stdio process, launched with uvx from the wechat-devtools-mcp PyPI package. Requires WeChat DevTools installed with its CLI, the WECHAT_DEVTOOLS_CLI path, a default project path in WECHAT_PROJECT_PATH, and optionally NODE_PATH and WECHAT_CLI_TIMEOUT. Desktop only; no web execution.
Before you install
The server can run DevTools CLI commands against your Mini Program project, which may build, preview or otherwise modify project state; review what each command does before letting an assistant run it. It needs local filesystem paths to the DevTools CLI and project, so avoid exposing unrelated directories.

Installation

In SourceWeft

  1. Open Wechat Devtools in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.