Skip to main content
Glama

Related Servers

Alternatives to Firecrawl MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform keyless web search, read pages past bot walls, look up product and local marketplace listings, fetch YouTube transcripts, and run multi-step research through MCP tools.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform live web searches across 9 engines, scrape web pages into clean formats, and run agentic research with citations via MCP.
      48 PyPI
      6
      MIT
    • A
      license
      A
      quality
      B
      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.
      27
      448 npm
      1
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables language models to perform AI-powered web scraping, structured data extraction, search, crawling, schema generation, and scheduled monitoring through a unified MCP interface. It provides tools for managing account credits, scrape history, and long-running crawl and monitor workflows.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to run web searches across configured providers and crawl individual pages or whole sites into clean Markdown or JSON, including authenticated crawls and local or HTTP MCP deployment.
      -

    TDQS

    A3.6/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action (scrape vs map vs crawl vs parse vs interact), and the specialized searches (developer, gov, research, web) are scoped by source domain. The weakest boundaries are firecrawl_monitor_check vs firecrawl_monitor_checks and firecrawl_search vs firecrawl_find_tools, both of which require reading the descriptions to separate.

    Naming Consistency4/5

    A predictable firecrawl_<noun>_<action> snake_case pattern dominates (scrape, map, crawl, monitor_create/update/delete, research_*_paper). A few names drop the verb or invert order — firecrawl_agent_status, firecrawl_credit_usage, firecrawl_find_tools — which are minor deviations but still readable.

    Tool Count3/5

    At 26 tools the surface is heavy, though the server genuinely spans several domains (scrape/crawl, agent, monitors, research, specialized search, billing). The monitor family alone is seven tools, and some pairs (monitor_run, agent_status) could plausibly be folded into existing operations.

    Completeness4/5

    Coverage is broad and lifecycle-complete in most areas: monitors have full CRUD plus run/checks, interact has a stop, agent has status polling, and research papers have search/inspect/related/read. Minor gaps remain — no crawl cancellation or batch-scrape operation, and job control is limited to read-only status checks.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues