Skip to main content
Glama
readdown-mcp
by zcag

readdown-mcp

MCP server for converting web pages to clean, LLM-optimized Markdown.

Lightweight — uses HTTP fetch, no browser needed. Powered by readdown.

Tools

fetch_markdown

Fetch a URL and convert it to clean Markdown with metadata and token count.

convert_html

Convert an HTML string to Markdown. Use when you already have the HTML.

Related MCP server: skrape

Install

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "readdown": {
      "command": "npx",
      "args": ["-y", "github:zcag/readdown-mcp"]
    }
  }
}

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "readdown": {
      "command": "npx",
      "args": ["-y", "github:zcag/readdown-mcp"]
    }
  }
}

Why readdown?

Most web-fetching MCP servers use @mozilla/readability + turndown (two packages, 65KB). readdown replaces both in a single 5KB package with better LLM optimization:

  • Token-efficient output (fewer tokens = cheaper API calls)

  • Built-in token estimation

  • Metadata extraction (title, author, date)

  • Works server-side with linkedom (no browser DOM needed)

License

MIT

Available Tools

2 tools
convert_htmlA

Convert an HTML string to clean, LLM-optimized Markdown. Use this when you already have HTML content and need it as Markdown.

Inputs: html (required), url, include_header, raw.

fetch_markdownA

Fetch a web page and convert it to clean, LLM-optimized Markdown. Returns the article content with metadata (title, author, date) and token count. Much faster and lighter than browser-based solutions.

Inputs: url (required), include_header, raw.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: convert_html processes existing HTML strings, while fetch_markdown retrieves and processes web pages. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (convert_html and fetch_markdown), using clear action verbs that describe their operations. The naming is predictable and aligned with their functions.

    Tool Count3/5

    With only two tools, the server feels minimal for a web content processing domain. While the tools cover core use cases, the scope is thin, potentially limiting agent workflows without additional operations like batch processing or format validation.

    Completeness4/5

    The tools provide essential coverage for converting HTML to Markdown, both from strings and web pages. However, there are minor gaps, such as no tool for reverse conversion (Markdown to HTML) or handling specific HTML elements, which agents might need to work around.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Converts any webpage into clean, LLM-ready Markdown, removing noise and supporting JavaScript rendering.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Fetch any web page as clean Markdown or plain text, split it into heading-aware, token-bounded RAG chunks, convert raw HTML, and read page metadata. Uses the Web2MD API on RapidAPI with your own key (free BASIC plan).
      4
      4
      47 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and LLM pipelines to fetch and crawl web pages, extract readable content, and convert it into clean Markdown with preserved links while minimizing token usage.
      MIT