Skip to main content
Glama
lexiismadd

Crawl4AI Complete MCP

by lexiismadd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Crawl4AI Complete MCP

No user-submitted related servers found.

    Related Servers

    • servo-fetch

      konippi
      A
      license
      A
      quality
      A
      maintenance
      Servo-powered MCP server for JS-aware web fetching, content extraction, crawling, and software-rendered screenshots — Chromium-free single binary.
      6
      148
      Apache 2.0

    • Shark-no-Kari

      HaiNick
      A
      license
      Not graded
      quality
      A
      maintenance
      Remote MCP server for web scraping with anti-bot evasion. Provides stealth HTTP fetching, headless browser with Cloudflare bypass, CSS selectors, YouTube transcripts, and Markdown conversion.
      1
      MIT

    • turbowebfetch

      aza-ali
      A
      license
      A
      quality
      B
      maintenance
      MCP server that lets Claude Code fetch web content using real Chrome browsers. Renders JavaScript-heavy pages, handles bot mitigation, and runs up to 14 parallel browsers locally with zero API keys. Makes outbound HTTP requests only to URLs the user explicitly asks Claude to fetch.
      2
      14 npm
      91
      MIT

    • Python Crawling MCP

      BaektotheFuture98
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for safe web crawling and scraping of public and authenticated sites using Playwright and Crawlee. It provides tools for scraping single pages, crawling entire sites, validating sessions, and listing supported sites, with built-in security protections and adapter-based extensibility.
      -
    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 15 tools

    Disambiguation3/5

    Crawl, crawl_stream, and crawl_job_submit present overlapping crawling functionality, while extract and llm_job_submit both offer LLM-based extraction. These clusters create ambiguity, though most other tools are clearly distinct.

    Naming Consistency3/5

    Tool names mix single nouns (screenshot, pdf, html), bare verbs (extract, crawl), verb_noun forms (execute_js, crawl_stream), and noun_verb constructions (crawl_job_submit, job_status). The inconsistent pattern makes it harder to predict tool names, though all are readable and lowercase.

    Tool Count5/5

    15 tools for a 'Complete' MCP covering crawling, extraction, rendering, and job management is well-scoped. Each tool adds a distinct capability without unnecessary bloat.

    Completeness4/5

    The surface covers core workflows: fetch content, crawl (sync/stream/async), extract (sync/LLM), check job status, and retrieve artifacts. Minor gaps like job cancellation or listing jobs are absent but not critical.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources