WeChat MCP Server
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_wechat_statusA | 检查微信客户端连接状态、窗口可见性与自动化后端是否可用。 |
| get_chat_listB | 返回当前可读取的会话列表。基于监听期间被动接收到的消息，不是微信完整会话列表。 |
| get_chat_historyB | 读取指定会话在缓冲区内最近的消息。需明确指定会话名称；返回数量受缓冲区容量限制。 |
| send_messageB | 向明确指定的联系人或群聊发送文本消息。目标不唯一时拒绝发送并返回候选列表；无法确认发送成功时返回失败状态，不自动重试。 |
| search_contactA | 按名称搜索联系人/群聊，返回候选列表。同名时原样返回多个候选，不自行猜测，需由调用方进一步指定。 |
| get_chat_infoC | 返回指定会话已确认可获取的信息：名称、类型、观察到的消息数与最后时间，以及该会话当前是否在关注列表中。 |
| send_fileA | 向明确指定的联系人或群聊发送本地文件。文件必须存在且位于允许目录内；未配置可发送目录时拒绝发送。结果无法确认时返回失败，不自动重试。 |
| get_recent_messagesA | 增量读取监听缓冲区中新增的消息。传入上次返回的 next_seq 作为 after_seq，即可只获取新消息。可选用 chat_name 限定单个会话。 |
| set_monitored_chatsA | 设置会话关注列表：add/remove 增删会话名，mode 选择 allow（白名单，空=全部）或 block（黑名单，优先级更高）。仅过滤本服务返回的读取结果，不改变底层监听行为。 |
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 9 tools
Most tools have clearly distinct purposes: status, chat listing, contact search, sending, and monitoring are separate. There is some overlap between get_chat_history and get_recent_messages since both retrieve messages, but the descriptions clarify buffer-based history versus incremental sequence-based reading.
All tool names follow a consistent snake_case verb_noun pattern (get_*, send_*, search_*, set_*). No mixed conventions or ambiguous verb styles are present.
9 tools is well within the ideal 3-15 range and each appears to cover a necessary capability for WeChat automation. The set is neither bloated nor too thin for the domain.
The surface covers status, chat listing, message history, sending text/files, contact search, and monitoring configuration. Minor gaps such as retrieving full chat history beyond the buffer or fetching detailed contact information exist but are workable around.