Skip to main content
Glama
crawlbrulee

@crawlbrulee/mcp

Official
by crawlbrulee

Related Servers

Alternatives to @crawlbrulee/mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI agents to search, scrape, crawl, map, and interact with live web pages, returning clean, structured, agent-ready content. It also supports recurring page monitoring, autonomous deep research, and credit-usage checks.
      129,393 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to scrape web pages into Markdown, text, HTML, JSON, PDFs, screenshots, and structured data, while managing batch scraping jobs, persistent browser sessions, usage/request history, and docs lookup through native MCP tools.
      914 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to scrape, crawl, map, search, and extract web pages as clean markdown or structured JSON directly through MCP tools.
      AGPL 3.0
    • A
      license
      A
      quality
      D
      maintenance
      MCP-native web scraping and search API for AI agents. Converts any URL to clean Markdown with 90% success rate, including Cloudflare-protected sites and JS SPAs. Real-time web search via Brave Search API. CAPTCHA solving built-in. 10 free scrapes/day.
      5
      2 npm
      5
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An APAC-native web scraping API for AI agents that provides tools for scraping, crawling, searching, and extracting structured data from websites, directly usable from MCP-compatible clients like Claude Desktop, Cursor, and Windsurf.
      7
      6 npm
      MIT

    TDQS

    A4.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: scrape (sync), scrape_async (async submit), scrape_status (poll), scrape_result (fetch result), map (site discovery), whoami (account identity), and usage (billing). The async pipeline tools are cleanly separated by their lifecycle stage, and no two tools could be reasonably confused.

    Naming Consistency4/5

    All names use snake_case and the scrape family shares a consistent prefix (scrape, scrape_async, scrape_status, scrape_result). Minor deviation exists because some tools are noun-like (usage, status) while others are verb-like (scrape, map), but overall the pattern is predictable.

    Tool Count5/5

    Seven tools is well-scoped for a scraping/crawling API, covering synchronous scraping, asynchronous job management, site mapping, and account/billing introspection. Each tool earns its place and the set is neither bloated nor thin.

    Completeness4/5

    The surface covers the core lifecycle: single-page scrape, async submit/poll/fetch, site map, and account usage. A minor gap is the lack of a batch or whole-site crawl operation that would let an agent scrape multiple discovered URLs in one call, though map-then-scrape workflows are workable.

    Maintenance

    ActivityActive
    ResponsivenessNo issues