wemp-operator-mcp

wemp-operator-mcp

Enables to operate a WeChat Official Account via MCP tools, including searching and executing API workflows and uploading files.

Category
Visit Server

README

wemp-operator-mcp

Public HTTP MCP server and agent Skill for operating a WeChat Official Account.

The server is designed for public deployment behind HTTPS. It keeps WeChat credentials on the server, exchanges and caches access_token from a fixed egress IP, and exposes only two MCP tools to agents:

  • tool_search: discover the internal API/workflow catalog.
  • run_tool: execute one discovered internal tool.

The companion Skill configures a local agent to call your public MCP endpoint through mcporter.

Languages

Why One Repository

The MCP server and Skill are versioned together in this repository because the Skill documents the exact public contract exposed by the server. Keeping them together prevents schema drift between file upload handling, tool_search metadata, and run_tool examples.

Features

  • HTTP Streamable MCP endpoint at /mcp.
  • Bearer token authentication for every MCP and upload request.
  • Server-side WeChat access_token exchange using WEMP_WECHAT_APP_ID and WEMP_WECHAT_APP_SECRET.
  • Token cache with early refresh, single-flight refresh, and one retry after WeChat token-expired responses.
  • Temporary file upload endpoint at /uploads for remote MCP file tools.
  • HTTPS URL file source support with SSRF protections.
  • Dangerous tools are disabled by default, including publish/delete/mass-send and blacklist operations.
  • Local CLI remains available for development and local automation.

Architecture

Local Agent + Skill
        |
        | mcporter HTTP MCP
        v
HTTPS reverse proxy
        |
        v
wemp-operator-mcp container
        |
        | fixed public egress IP
        v
WeChat Official Account APIs

For public deployment, add your server's public egress IP to the WeChat Official Account API IP allowlist. Agents only need the MCP bearer token; they do not receive your WeChat AppSecret or access_token.

Public API

MCP

POST /mcp
Authorization: Bearer <WEMP_MCP_TOKEN>

Public MCP tools:

tool_search(query?: string, category?: string, limit?: number)
run_tool(name: string, arguments?: object)

Example:

mcporter call wemp-operator-mcp.tool_search \
  --args '{"query":"draft image","limit":10}' \
  --output json
mcporter call wemp-operator-mcp.run_tool \
  --args '{"name":"get_user_summary","arguments":{"date":"2026-06-21"}}' \
  --output json

File Upload

Remote MCP servers cannot read local paths from the caller machine. Upload the file first:

POST /uploads
Authorization: Bearer <WEMP_MCP_TOKEN>
Content-Type: multipart/form-data

The form must contain exactly one file field. Successful response:

{
  "uploadId": "cfa59bda-0d99-4ad7-9afe-77efb8b09c80",
  "filename": "cover.png",
  "mimeType": "image/png",
  "size": 123456,
  "expiresAt": "2026-06-21T12:00:00.000Z"
}

Use the returned uploadId with file tools:

mcporter call wemp-operator-mcp.run_tool \
  --args '{"name":"upload_article_image","arguments":{"source":{"uploadId":"cfa59bda-0d99-4ad7-9afe-77efb8b09c80"}}}' \
  --output json

Or pass a public HTTPS URL:

mcporter call wemp-operator-mcp.run_tool \
  --args '{"name":"upload_article_image","arguments":{"source":{"url":"https://example.com/image.png","filename":"image.png"}}}' \
  --output json

File source tools:

  • upload_temp_media
  • upload_permanent_media
  • upload_article_image
  • create_draft_from_file

MCP file tools intentionally do not accept filePath. Local CLI scripts may still use local paths.

Quick Start: Docker

  1. Clone the repository.
git clone https://github.com/xiaowangzhixiao/wemp-operator-mcp.git
cd wemp-operator-mcp
  1. Create an environment file.
cp .env.example .env

Edit .env:

WEMP_MCP_TOKEN=replace-with-a-random-token
WEMP_WECHAT_APP_ID=wx...
WEMP_WECHAT_APP_SECRET=replace-with-your-app-secret
WEMP_MCP_HOST=0.0.0.0
WEMP_MCP_PORT=3333
WEMP_MCP_ENABLE_DANGEROUS_TOOLS=0

Generate a token:

openssl rand -hex 32
  1. Run the server.
docker compose up -d --build
curl --fail http://127.0.0.1:3333/healthz
  1. Put Nginx or another HTTPS reverse proxy in front of the container.

Use deploy/nginx.example.conf as a starting point. Replace mcp.example.com with your own domain and set certificate paths for your certificate provider.

  1. Add your server public IP to the WeChat Official Account allowlist.

In the WeChat Official Account admin console, go to the developer settings and add the public egress IP of the server running this container.

Environment Variables

Required:

  • WEMP_MCP_TOKEN: bearer token for MCP and upload requests.
  • WEMP_WECHAT_APP_ID: WeChat Official Account AppID.
  • WEMP_WECHAT_APP_SECRET: WeChat Official Account AppSecret.

Optional:

  • WEMP_MCP_HOST: default 127.0.0.1; use 0.0.0.0 in containers.
  • WEMP_MCP_PORT: default 3333.
  • WEMP_WECHAT_TOKEN_REFRESH_SKEW_SECONDS: default 300.
  • WEMP_MCP_ENABLE_DANGEROUS_TOOLS: set 1 to enable dangerous tools.
  • WEMP_MCP_UPLOAD_MAX_BYTES: default 52428800 (50 MiB).
  • WEMP_MCP_UPLOAD_TOTAL_BYTES: default 524288000 (500 MiB).
  • WEMP_MCP_UPLOAD_TTL_SECONDS: default 900.

Do not log or commit .env, AppSecret, WeChat access_token, or MCP bearer tokens.

Install The Agent Skill

The Skill lives at:

skills/wemp-operator-mcp

For Codex-style local skills:

npm run skill:install

Configure the MCP endpoint:

cd skills/wemp-operator-mcp
WEMP_MCP_URL='https://mcp.example.com/mcp' \
WEMP_MCP_TOKEN='<your-mcp-token>' \
node scripts/setup.mjs

Verify:

mcporter list wemp-operator-mcp
mcporter call wemp-operator-mcp.tool_search --args '{"limit":10}' --output json

Upload a local file through the Skill helper:

WEMP_MCP_URL='https://mcp.example.com/mcp' \
WEMP_MCP_TOKEN='<your-mcp-token>' \
node scripts/upload-file.mjs /absolute/path/to/cover.png

Local Development

Use Node.js 20.12 or newer.

Install dependencies:

npm install

Run tests:

npm test

Start a local MCP server:

WEMP_MCP_TOKEN=dev-token \
WEMP_WECHAT_APP_ID=wx... \
WEMP_WECHAT_APP_SECRET=... \
npm run mcp:start

Local CLI mode can still use config/wemp.json through:

node scripts/init.mjs

That local config is not used in MCP context.

Deployment Guides

Security Defaults

  • MCP and upload routes require the same bearer token.
  • Only tool_search and run_tool are public MCP tools.
  • The server never exposes AppSecret or WeChat access_token through MCP.
  • Dangerous operations are disabled unless WEMP_MCP_ENABLE_DANGEROUS_TOOLS=1.
  • File uploads are temporary and are deleted after TTL.
  • Public URL fetching only allows HTTPS and rejects private, loopback, link-local, multicast, and cloud metadata network ranges.

License

MIT

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured