Wenyan MCP Server

MCP server for Wenyan, a Markdown formatting tool that allows AI assistants to apply elegant built-in themes and publish articles directly to 微信公众号.

Local serverstdio

What is the Wenyan MCP MCP server?

If you already use Wenyan MCP, the wenyan mcp mcp server is the piece that lets your assistant work with it directly. MCP server for Wenyan, a Markdown formatting tool that allows AI assistants to apply elegant built-in themes and publish articles directly to 微信公众号.

What the server does

基于 MCP 协议,Claude Desktop 等 AI 客户端现在可以直接调用文颜(Wenyan)的排版引擎。写完文章后,不需要再去第三方编辑器里来回复制粘贴,直接让 AI 帮你排版并塞进微信草稿箱。

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • WECHAT_APP_ID — WECHAT_APP_SECRET
  • title — ✅
  • cover — ❌
  • author — ❌
  • source_url — ❌
  • type — ❌
  • image_list — ❌
  • need_open_comment — ❌
  • only_fans_can_comment — ❌

Credentials and setup notes

Configuration is passed through the environment: WECHAT_APP_ID, WECHAT_APP_SECRET, HOST_FILE_PATH, MCP_PROXY_AUTH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

The server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Wenyan MCP's toolset — WECHAT_APP_ID, title, cover and 6 more — is a fair guide to whether it matches your workflow. It is maintained by caol64; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Wenyan MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Wenyan MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
WECHAT_APP_IDWECHAT_APP_SECRET
title
cover
author
source_url
type
image_list
need_open_comment
only_fans_can_comment

How to install the Wenyan MCP MCP server

* **Claude Desktop 配置:**:

```json
{
  "mcpServers": {
    "wenyan-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-v", "/your/host/file/path:/mnt/host-downloads",
        "-e", "WECHAT_APP_ID=your_app_id",
        "-e", "WECHAT_APP_SECRET=your_app_secret",
        "-e", "HOST_FILE_PATH=/your/host/file/path",
        "caol64/wenyan-mcp"
      ]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
WECHAT_APP_IDConfiguration value read at startup.Optional
WECHAT_APP_SECRETCredential the server authenticates with.Yes
HOST_FILE_PATHEndpoint or connection string the server talks to.Optional
MCP_PROXY_AUTH_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Wenyan MCP to WECHAT APP ID.
  • Use Wenyan MCP to title.
  • Use Wenyan MCP to cover.

Frequently asked questions

It connects Wenyan MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (WECHAT_APP_ID, title, cover, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Wenyan MCP directly.