wechat-reader
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WECHAT_READER_PROFILE | No | Directory for the browser profile used in browser mode. Defaults to ~/.wechat-reader/browser-profile and does not read the daily Chrome personal profile. This directory stores browsing session data and should not be uploaded. | ~/.wechat-reader/browser-profile |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_wechat_articleA | Read a public https://mp.weixin.qq.com/s/... article, returning text and metadata. Omit use_browser (or use null) to try HTTP and automatically open dedicated visible Chrome on a verification page. True uses Chrome directly; False disables the browser. Any remaining captcha requires the user to verify manually. wait_seconds is 0–30. Continue a long article by passing next_offset as offset. Images are returned as links, with no OCR. |
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 1 tool
There is only one tool, so there is no possibility of misselection between tools. Its purpose (read a public mp.weixin.qq.com article) is stated unambiguously.
The single name read_wechat_article follows a clear verb_noun snake_case convention that describes exactly what it does. No mixed conventions exist to worry about.
One tool is on the thin side, but the server's domain is genuinely a single operation (fetch one WeChat article), and the tool absorbs pagination, browser fallback, and metadata into parameters rather than extra tools. Adding more tools would be artificial padding.
The read lifecycle is covered: HTTP-first fetch, browser fallback for verification pages, offset-based continuation for long articles, and metadata plus image links. Minor gaps remain (no batch/multi-article read, no OCR, no article discovery), but these are outside the stated purpose and agents can work around them.