WeChat_get_access_tokenLABSCO SUMMARY
A drop-in replacement for the Python version, shipped as one file.
The five tools cover the whole draft-to-publish loop, and deleting a draft before it goes out is there too, which matters when a model produces something you would rather not send. Because it is a single static binary the install is a copy rather than a dependency tree — the trade-off is that you build it yourself, as there is no package registry entry.
What it is
A Go rewrite of a WeChat Official Account MCP server, built on the mark3labs/mcp-go framework. It keeps the same tool names, arguments and responses as the earlier Python version, so it drops into an existing setup, and it ships as one binary or a container image.
What you get
WeChat_get_access_tokenfetches the account access token the other calls needWeChat_create_draftcreates an article draftWeChat_publish_draftpublishes a draft to the accountWeChat_del_draftdeletes a draft that has not gone out yetWeChat_del_materialremoves a permanent media asset- Structured logs go to stderr, including which tools registered and how each request was handled
Requirements
Go source with a Makefile: make build produces bin/wechat-oa-mcp, or make docker-run builds and runs the container image wechat-oa-mcp-go:latest. Point your client at the binary path, or at docker run -i --rm. LOG_LEVEL controls verbosity — set it to debug when a call is failing.
Setup effort
Run a container — build the image from the repository, then point your client at it
USE CASES
01
Turning a piece of writing into a draft
Hand over the article and have it land in the account's drafts instead of being pasted into the web editor.
02
Publishing once you have read it back
Review the draft yourself, then publish it in the same conversation.
03
Throwing away a bad draft
Delete the draft before it goes out, rather than leaving it in the account.
04
Working out why a call failed
Set the log level to debug and read the tool registration and request handling on stderr.
5 tools
Listed in project docs. Your client may show a different list.
WeChat_create_draftWeChat_publish_draftWeChat_del_draftWeChat_del_materialBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
docker on PATH
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Build the image from the repository, then point your client at it.
Server setup
Docker image (built locally)
TERMINAL
git clone https://github.com/tc6-01/weixin-mcp.git
cd weixin-mcp
docker build -t wechat-oa-mcp-go:latest .Local binary
TERMINAL
git clone https://github.com/tc6-01/weixin-mcp.git
cd weixin-mcp
make deps
make buildMCP Clients
Cursor — local binary
CURSOR — LOCAL BINARY · JSON
{
"mcpServers": {
"wechat-oa-mcp-go": {
"command": "<YOUR_PATH_TO_WECHAT_OA_MCP_GO>/bin/wechat-oa-mcp",
"env": {
"LOG_LEVEL": "info"
}
}
}
}<YOUR_PATH_TO_WECHAT_OA_MCP_GO> is the full path of your weixin-mcp clone. Make build writes the binary to bin/wechat-oa-mcp there.
Cursor — Docker
CURSOR — DOCKER · JSON
{
"mcpServers": {
"wechat-oa-mcp-go": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"wechat-oa-mcp-go:latest"
]
}
}
}wechat-oa-mcp-go:latest is the image the docker build step above creates on your machine; it is not pulled from a registry.
