MCP Firecrawl Server

Related Servers

Alternatives to MCP Firecrawl Server

No user-submitted related servers found.

Related Servers

MCP Server Firecrawl
Web Scraping Search Browser Automation
Msparihar
A
license
C
quality
D
maintenance
A server that provides web scraping and intelligent content searching capabilities using the Firecrawl API, enabling AI agents to extract structured data from websites and perform content searches.
Updated 2 years ago (2025-02-13 15:44 UTC)
5
3
MIT
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.
Updated a year ago (2025-07-15 05:56 UTC)
8
199,364 npm
2
MIT
Firecrawl MCP Server
Web Scraping RAG Systems Browser Automation
mcma123
A
license
B
quality
D
maintenance
A Model Context Protocol server that enables AI assistants to perform advanced web scraping, crawling, searching, and data extraction through the Firecrawl API.
Updated 2 years ago (2025-03-10 04:55 UTC)
9
199,364 npm
MIT
Firecrawl MCP Multiple Keys
Web Scraping Search Research & Data
AdvaitR7
A
license
A
quality
D
maintenance
A Firecrawl MCP server with built-in support for multiple API key rotation, enabling web search, scraping, crawling, extraction, and more via MCP clients.
Updated 2 months ago (2026-07-16 03:42 UTC)
26
3
MIT
WebSearch
Web Scraping Browser Automation Search
josemartinrodriguezmortaloni
F
license
C
quality
C
maintenance
Built as a Model Context Protocol (MCP) server that provides advanced web search, content extraction, web crawling, and scraping capabilities using the Firecrawl API.
Updated 3 months ago (2026-06-17 03:44 UTC)
4
1
-
firecrawl-simple-mcp
Browser Automation Web Scraping
Sacode
A
license
Not graded
quality
D
maintenance
Empowers LLMs to scrape web pages and generate sitemaps through the Firecrawl Simple API, with support for JavaScript rendering and configurable options.
Updated a year ago (2025-04-08 16:01 UTC)
4 npm
1
MIT

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

D1.4/5.0

Scored 2026-04-18 11:25 across 2 tools

Disambiguation2/5

The two tools have overlapping purposes that could cause confusion. 'extract-data' and 'scrape-website' both appear to involve retrieving data from websites, with no clear distinction in their descriptions. While they might target different aspects of web data extraction, the lack of descriptions makes it impossible to determine their boundaries, leading to potential misselection.

Naming Consistency4/5

The tool names follow a consistent snake_case pattern with verb_noun structure (extract-data, scrape-website). Both use clear action verbs ('extract' and 'scrape') paired with nouns ('data' and 'website'), making them readable and predictable. There are no deviations in naming style across the two tools.

Tool Count2/5

With only 2 tools, the server feels under-scoped for a web scraping/ data extraction domain, which typically requires more operations like configuration, filtering, or handling different data formats. This limited set may force agents to work around gaps, as basic CRUD or lifecycle coverage is incomplete.

Completeness1/5

The tool surface is severely incomplete for a web scraping server. There are obvious gaps such as no tools for configuring scraping parameters, handling authentication, managing jobs, or processing extracted data. Without descriptions, it's unclear what these tools do, but the lack of supporting operations suggests agents will face dead ends in typical workflows.