WeChat Publisher MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wechat_publish_articleC | 将文章发布到微信公众号，支持Markdown格式 |
| wechat_query_statusC | 查询文章发布状态和统计数据 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one publishes articles and the other queries status/statistics. There is no overlap in functionality, making it impossible to confuse them.
Both tools follow a consistent 'wechat_verb_noun' pattern with snake_case. The naming is predictable and aligned with the server's domain.
With only two tools, the server feels thin for a 'publisher' domain. It lacks basic operations like drafting, editing, deleting articles, or managing media, which are typical in content publishing workflows.
The toolset is severely incomplete for publishing. It covers publishing and status querying but misses essential CRUD operations (e.g., create drafts, update articles, delete posts) and other common features like media uploads or audience analytics.