Skip to main content
Glama
MarekCziba

Website to Markdown MCP

by MarekCziba

Related Servers

Alternatives to Website to Markdown MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Fetch web pages into clean, RAG-ready Markdown with a verifiable provenance record — source URL, UTC fetch time, SHA-256 of the response body, redirect chain, and an extraction-fidelity metric. Writes WARC archives and honours robots.txt/ai.txt, so every document an agent reads can be re-verified and cited.
      141 PyPI
      2
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and MCP clients to fetch web pages and distill them into clean, token-efficient markdown by stripping cookie banners, navigation bars, and ads. Runs with zero external dependencies over JSON-RPC stdio, delivering deterministic sub-millisecond results without LLM round-trips.
      7
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to read web pages reliably, returning clean markdown content, hyperlinks, and metadata without navigation or ad noise.
      3
      6 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Fetch URLs and return clean, LLM-ready markdown with metadata and layered prompt injection defense. Configurable timeouts, word limits, JS rendering, and link extraction. All-in-one MCP server + CLI.
      1
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Fast, token-efficient web content extraction tool that converts websites to clean Markdown for AI agents, featuring smart caching, content extraction with Mozilla Readability, and polite crawling capabilities.
      1
      402 npm
      160
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Converts any web page URL into clean Markdown for LLM context (Claude, ChatGPT, etc.) with zero external API calls, running entirely locally.
      1
      66 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation4/5

    fetch_url and fetch_urls share nearly identical purpose, differing only in single vs. batch input, but their descriptions make the distinction explicit. extract_metadata targets a clearly different output (page metadata) and stands apart cleanly.

    Naming Consistency5/5

    All three names follow a consistent snake_case verb_noun pattern (fetch_url, fetch_urls, extract_metadata). The plural form for the batch variant is a sensible, predictable convention.

    Tool Count4/5

    Three tools is on the lean side but well-matched to a narrow single-purpose server (web page to Markdown conversion). Each tool earns its place with no redundancy.

    Completeness4/5

    Covers the core surface: single fetch, concurrent batch fetch, and metadata extraction, with a sensible max_length control. Missing niceties like custom headers/auth or content-selector options, but no dead ends for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues