Skip to main content
Glama
SunZhi-Will

Website to Markdown MCP Server

by SunZhi-Will
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Website to Markdown MCP Server

No user-submitted related servers found.

    Related Servers

    • Puppeteer Vision MCP Server

      djannot
      A
      license
      Not graded
      quality
      C
      maintenance
      Scrapes webpages and converts them to markdown using AI-powered interaction to automatically handle cookie banners, CAPTCHAs, paywalls, and other blocking elements before extracting clean content.
      8 npm
      48
      Apache 2.0

    • skrape

      AmokOrg
      A
      license
      Not graded
      quality
      D
      maintenance
      Converts any webpage into clean, LLM-ready Markdown, removing noise and supporting JavaScript rendering.
      MIT

    • MCP HTTP Fetcher Server

      photonn
      A
      license
      Not graded
      quality
      F
      maintenance
      Fetches web pages from HTTP/HTTPS URLs and converts them to Markdown format. Supports both SSE and Stdio protocols for web deployments, Kubernetes environments, and desktop clients.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 4 tools

    Disambiguation2/5

    There is significant overlap and ambiguity among the fetch tools. fetch_example_site and fetch_test_site are essentially special cases of fetch_website, making it unclear when to use which. An agent might struggle to choose between them, as the descriptions don't clarify distinct use cases beyond different hardcoded URLs.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern throughout (fetch_example_site, fetch_test_site, fetch_website, list_configured_websites). All use snake_case and start with descriptive verbs, making the naming predictable and easy to understand.

    Tool Count3/5

    With 4 tools, the count is borderline for the server's purpose of converting websites to markdown. It feels slightly thin, as there could be more operations like updating configurations or handling errors, but it covers basic fetching and listing. It's not extreme, but could be more robust.

    Completeness2/5

    There are significant gaps in the tool surface. The server lacks tools for configuring or managing websites beyond listing them (e.g., add_website, remove_website, update_configuration). This incompleteness will likely cause agent failures when trying to perform full lifecycle operations, as the current set is limited to fetching and listing only.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources