web-reader-mcp
Related Servers
Alternatives to web-reader-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to read web pages reliably, returning clean markdown content, hyperlinks, and metadata without navigation or ad noise.36 npmMIT
- AlicenseBqualityDmaintenanceEnables LLMs to retrieve and process web content by fetching URLs and converting HTML to markdown format. Supports chunked reading of large pages and can access both public websites and local networks.1MIT
- AlicenseAqualityDmaintenanceEnables LLMs to fetch and process web content by converting HTML into markdown for easier consumption. It supports chunked reading via pagination and provides configuration options for robots.txt compliance and proxy usage.1MIT
- AlicenseAqualityDmaintenanceEnables AI agents to fetch any web page as clean markdown or screenshot it, turning URLs into LLM-ready context.21 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read, screenshot, or convert web pages to PDF using a real headless browser, turning any URL into clean Markdown, a visual image, or a print-ready document.82 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables LLM agents to fetch web pages and receive clean, readable markdown with token budgeting and link extraction.1MIT
TDQS
Scored across 4 tools
Each tool has a distinct primary role: read content, list links, get outline, or find literal text. The only real overlap is between find_in_page and read_page's query mode, since both can return relevant passages, but the descriptions distinguish exact/regex matching from answer-oriented extraction.
All names are lowercase snake_case and share the 'page' vocabulary, making them readable, but the pattern is mixed: find_in_page and read_page are verb-first while page_links and page_outline are noun-first. This is not chaotic, but it is not a uniform verb_noun convention.
Four tools is well-scoped for a web reader server: read, search, list links, and outline cover the core interactions without redundancy or bloat. Every tool earns its place in the set.
The tool surface covers the main web-reading workflow: fetching clean content, navigating via links, finding specific text, and using headings to selectively read sections. There are no obvious dead ends—page_links and page_outline feed naturally into read_page, and find_in_page complements full-page reading.