Skip to main content
Glama
bidouilles

cloudflare-crawl-mcp

by bidouilles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to cloudflare-crawl-mcp

No user-submitted related servers found.

    Related Servers

    • scribe-me

      jlehman
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server to scrape web pages to clean Markdown via headless Chromium, with support for single or batch URLs.
      -
    • redup.mcp-web-parser by redup-ai

      redup.mcp-web-parserofficial

      redup-ai
      A
      license
      A
      quality
      A
      maintenance
      MCP server that parses web pages into clean markdown via Crawl4AI's HTTP API, exposing parse_page and health-check tools with configurable proxy and timeout.
      2
      MIT

    • fetch-rendered-page-mcp

      blono
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that fetches and renders dynamic web pages (SPA) using Chromium, returning content as Markdown or text. It uses lightweight HTTP first with automatic fallback to a browser for JS-heavy sites, and includes SSRF protection, login session support, and batch fetching.
      -
    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

    A4.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: scrape_url fetches one page, map_url discovers URLs without fetching content, and crawl_url fetches multiple pages. The descriptions explicitly state when to use each, so there is no ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores: scrape_url, map_url, crawl_url. The style is uniform and predictable, making it easy to infer functionality.

    Tool Count5/5

    Three tools is well-scoped for a crawling server. Each tool covers a distinct core operation—single fetch, URL discovery, and bulk crawl—without unnecessary redundancy or bloat.

    Completeness4/5

    The tools cover the essential crawl lifecycle: discover URLs, scrape a single page, and crawl multiple pages. Minor gaps exist (e.g., no sitemap parsing or headless options for custom headers), but the core workflows are complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources