Firecrawl MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIRECRAWL_API_KEY | No | Your Firecrawl API key (required for cloud API, optional for self-hosted instances) | |
| FIRECRAWL_API_URL | No | Custom API endpoint for self-hosted instances (e.g., https://firecrawl.your-domain.com). If not provided, the cloud API will be used. | |
| FIRECRAWL_RETRY_MAX_DELAY | No | Maximum delay in milliseconds between retries | 10000 |
| FIRECRAWL_RETRY_MAX_ATTEMPTS | No | Maximum number of retry attempts for rate-limited requests | 3 |
| FIRECRAWL_RETRY_INITIAL_DELAY | No | Initial delay in milliseconds before first retry | 1000 |
| FIRECRAWL_RETRY_BACKOFF_FACTOR | No | Exponential backoff multiplier | 2 |
| FIRECRAWL_CREDIT_WARNING_THRESHOLD | No | Credit usage warning threshold | 1000 |
| FIRECRAWL_CREDIT_CRITICAL_THRESHOLD | No | Credit usage critical threshold | 100 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| firecrawl_scrapeA | Scrape a single webpage with advanced options for content extraction. Supports various formats including markdown, HTML, and screenshots. Can execute custom actions like clicking or scrolling before scraping. |
| firecrawl_mapC | Discover URLs from a starting point. Can use both sitemap.xml and HTML link discovery. |
| firecrawl_crawlB | Start an asynchronous crawl of multiple pages from a starting URL. Supports depth control, path filtering, and webhook notifications. |
| firecrawl_batch_scrapeC | Scrape multiple URLs in batch mode. Returns a job ID that can be used to check status. |
| firecrawl_check_batch_statusB | Check the status of a batch scraping job. |
| firecrawl_check_crawl_statusB | Check the status of a crawl job. |
| firecrawl_searchA | Search and retrieve content from web pages with optional scraping. Returns SERP results by default (url, title, description) or full page content when scrapeOptions are provided. |
| firecrawl_extractC | Extract structured information from web pages using LLM. Supports both cloud AI and self-hosted LLM extraction. |
| firecrawl_deep_researchC | Conduct deep research on a query using web crawling, search, and AI analysis. |
| firecrawl_generate_llmstxtB | Generate standardized LLMs.txt file for a given URL, which provides context about how LLMs should interact with the website. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools have distinct purposes, such as scrape vs. crawl vs. extract, but there is some potential confusion between firecrawl_batch_scrape and firecrawl_scrape, as both involve scraping with overlapping functionality. The descriptions clarify that batch handles multiple URLs asynchronously, while single scrape is for one page with advanced options, but an agent might still misselect without careful reading.
All tool names follow a consistent snake_case pattern with a 'firecrawl_' prefix and descriptive verb_noun combinations, such as firecrawl_scrape, firecrawl_crawl, and firecrawl_extract. This uniformity makes the tool set predictable and easy to navigate for an agent.
With 10 tools, the count is well-scoped for a web crawling and scraping server, covering key operations like scraping, crawling, extracting, searching, and status checks. Each tool appears to earn its place without being excessive or insufficient for the domain.
The tool set provides comprehensive coverage for web data extraction, including single and batch scraping, crawling, mapping, searching, and AI-enhanced extraction. A minor gap is the lack of a tool for managing or deleting jobs, but core workflows are well-supported, and agents can likely work around this with the provided status-check tools.