wechat-reader
Related Servers
Alternatives to wechat-reader
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables fetching, searching, and summarizing WeChat public account articles through browser automation. Supports multiple output formats and provides article metadata and statistics.-
- AlicenseNot gradedqualityDmaintenanceEnables reading and extracting content from WeChat public account articles using browser automation, allowing AI models to analyze and summarize WeChat articles through natural language requests.465MIT
- FlicenseNot gradedqualityDmaintenanceEnables parsing and extracting content from WeChat public account articles using browser simulation, supporting multiple output formats (JSON, Markdown, HTML) and media resource extraction.-
- AlicenseAqualityCmaintenanceEnables crawling WeChat Official Account articles via the mp.weixin.qq.com search interface, including account search, article listing, incremental crawling, and fetching articles as Markdown with local SQLite storage.261MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI to read full-text WeChat Official Account articles, returning title, author, publish time, and clean Markdown content.9AGPL 3.0
- AlicenseAqualityCmaintenanceEnables agents to retrieve public WeChat Official Account articles as clean Markdown or JSON and parse saved WeChat HTML through MCP tools.22MIT
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.