Skip to main content
Glama
mcma123

Firecrawl MCP Server

by mcma123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to Firecrawl MCP Server

No user-submitted related servers found.

    Related Servers

    • Firecrawl MCP Server

      ampcome-mcps
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables web scraping, crawling, and content extraction capabilities through integration with Firecrawl.
      8
      22,552 npm
      2
      MIT

    • MCP Firecrawl

      mustafamemon265789-cloud
      F
      license
      A
      quality
      D
      maintenance
      A production-ready Model Context Protocol (MCP) server that integrates with the Firecrawl API to give AI assistants the power to scrape, crawl, and search the web.
      3
      -

    • tavily-firecrawl-mcp

      bpzx
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server for web scraping and searching, with automatic fallback from Tavily to Firecrawl for fetching web content.
      2
      1
      MIT
    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.4/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some potential overlap between firecrawl_scrape and firecrawl_extract, as both involve extracting content from web pages. The descriptions clarify that scrape focuses on raw content extraction with advanced options, while extract uses LLM for structured information, but an agent might still confuse them. Other tools like crawl, map, search, and deep_research are clearly differentiated.

    Naming Consistency5/5

    All tool names follow a consistent 'firecrawl_' prefix with snake_case and descriptive verb_noun patterns (e.g., batch_scrape, check_batch_status, crawl, deep_research). This uniformity makes the set predictable and easy to navigate, with no deviations in naming conventions across the nine tools.

    Tool Count5/5

    With 9 tools, the count is well-scoped for a web crawling and scraping server, covering key operations like single and batch scraping, crawling, mapping, searching, and deep research. Each tool serves a specific function without redundancy, making the set comprehensive yet manageable for typical use cases.

    Completeness4/5

    The tool set covers the core web crawling and scraping domain effectively, including initiation, status checking, and various extraction methods. A minor gap exists in the lack of tools for managing or deleting jobs, but agents can work around this by relying on job IDs and status checks. Overall, the surface supports essential workflows without significant dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources