What can you do with this server?

The MCP Firecrawl Server is a tool for scraping websites and extracting structured data with the following capabilities: * Website Scraping: Extract content from websites in various formats (markdown, HTML, or plain text) * Structured Data Extraction: Extract specific data points using custom schemas and natural language prompts * Customizable Outputs: Support for complex data extraction schemas including nested objects and arrays * Error Tracking: Integrated with Sentry for monitoring performance and logging errors * API Integration: Requires a Firecrawl API token for accessing scraping capabilities

Which integrations are available for this server?

Used for configuration management, allowing users to set environment variables like API tokens in a .env file Supported as an output format for the scraped website content Used for package management and running the server Integrated for error tracking and performance monitoring of the MCP server

How do I use MCP Firecrawl Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP Firecrawl Server scrape https://news.ycombinator.com in markdown format" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

en es ja ko zh

MCP Firecrawl Server

by codyde

Overview Schema Related Servers Score Discussions

JavaScript

Remote

MCP Firecrawl Server

This is a simple MCP server that provides tools to scrape websites and extract structured data using Firecrawl's APIs.

Setup

Install dependencies:

npm install

Create a .env file in the root directory with the following variables:

FIRECRAWL_API_TOKEN=your_token_here
SENTRY_DSN=your_sentry_dsn_here

FIRECRAWL_API_TOKEN (required): Your Firecrawl API token
SENTRY_DSN (optional): Sentry DSN for error tracking and performance monitoring

Start the server:

npm start

Alternatively, you can set environment variables directly when running the server:

FIRECRAWL_API_TOKEN=your_token_here npm start

Related MCP server: WebSearch

Features

Website Scraping: Extract content from websites in various formats
Structured Data Extraction: Extract specific data points based on custom schemas
Error Tracking: Integrated with Sentry for error tracking and performance monitoring

Usage

The server exposes two tools:

scrape-website: Basic website scraping with multiple format options
extract-data: Structured data extraction based on prompts and schemas

Tool: scrape-website

This tool scrapes a website and returns its content in the requested formats.

Parameters:

url (string, required): The URL of the website to scrape
formats (array of strings, optional): Array of desired output formats. Supported formats are:
- "markdown" (default)
- "html"
- "text"

Example usage with MCP Inspector:

# Basic usage (defaults to markdown)
mcp-inspector --tool scrape-website --args '{
  "url": "https://example.com"
}'

# Multiple formats
mcp-inspector --tool scrape-website --args '{
  "url": "https://example.com",
  "formats": ["markdown", "html", "text"]
}'

Tool: extract-data

This tool extracts structured data from websites based on a provided prompt and schema.

Parameters:

urls (array of strings, required): Array of URLs to extract data from
prompt (string, required): The prompt describing what data to extract
schema (object, required): Schema definition for the data to extract

The schema definition should be an object where keys are field names and values are types. Supported types are:

"string": For text fields
"boolean": For true/false fields
"number": For numeric fields
Arrays: Specified as ["type"] where type is one of the above
Objects: Nested objects with their own type definitions

Example usage with MCP Inspector:

# Basic example extracting company information
mcp-inspector --tool extract-data --args '{
  "urls": ["https://example.com"],
  "prompt": "Extract the company mission, whether it supports SSO, and whether it is open source.",
  "schema": {
    "company_mission": "string",
    "supports_sso": "boolean",
    "is_open_source": "boolean"
  }
}'

# Complex example with nested data
mcp-inspector --tool extract-data --args '{
  "urls": ["https://example.com/products", "https://example.com/pricing"],
  "prompt": "Extract product information including name, price, and features.",
  "schema": {
    "products": [{
      "name": "string",
      "price": "number",
      "features": ["string"]
    }]
  }
}'

Both tools will return appropriate error messages if the scraping or extraction fails and automatically log errors to Sentry if configured.

Troubleshooting

If you encounter issues:

Verify your Firecrawl API token is valid
Check that the URLs you're trying to scrape are accessible
For complex schemas, ensure they follow the supported format
Review Sentry logs for detailed error information (if configured)

Available Tools

2 tools

extract-dataD

ParametersJSON Schema

Name	Required	Description	Default
`urls`	Yes
`prompt`	Yes
`schema`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

scrape-websiteD

ParametersJSON Schema

Name	Required	Description	Default
`url`	Yes
`formats`	No

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.4/5.0

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.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

GitHub Repository

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

xpay✦ Web Scraping Collection B
sh.xpay.mcp.scraping
40+ web scraping tools from Firecrawl, Bright Data, Jina, Olostep, ScrapeGraph, Notte, and Riveter. Scrape, crawl, screenshot, and extract from any website. Starts at $0.01/call. Get your API key at app.xpay.sh or xpay.tools
Web Scraping Browser Automation Developer Tools
3
Firecrawl A
io.github.pipeworx-io
Firecrawl MCP — wraps the Firecrawl API (firecrawl.dev) for web
Web Scraping Browser Automation
343
zenrows-mcp
io.github.ZenRows
Zenrows MCP server — Fetch, Extract, Batch, and Browser Sessions for AI coding assistants
Web Scraping Browser Automation
119
AI Website-to-JSON Data Scraper & Extractor
com.ranovam
Turn any website into structured JSON data matching your custom schema.
Browser Automation Web Scraping
1

Related MCP 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
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 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 a year ago (2025-03-10 04:55 UTC)
9
40,139
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
40,139
2
MIT

Appeared in Searches

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/codyde/mcp-firecrawl-tool'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

MCP Firecrawl Server

Setup

Features

Usage

Tool: scrape-website

Tool: extract-data

Troubleshooting

Available Tools

TDQS

TDQS

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

MCP Server Firecrawl

WebSearch

Firecrawl MCP Server

Firecrawl MCP Server

Appeared in Searches

Latest Blog Posts

MCP directory API