Firecrawl Local MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIRECRAWL_URL | No | The URL of the self-hosted Firecrawl instance. By default, it connects to http://localhost:3002. | http://localhost:3002 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| firecrawl_scrapeC | Scrape a single webpage and return its content in markdown format |
| firecrawl_crawlB | Crawl a website starting from a URL and return content from multiple pages |
| firecrawl_crawl_statusC | Check the status of a crawl job |
| firecrawl_mapC | Map a website to get a list of all accessible URLs |
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 4 tools
Each tool targets a distinct operation: starting a crawl, checking its status, mapping a site's URLs, and scraping a single page. No overlap in purpose.
All tools share the 'firecrawl_' prefix and use verb-style names. However, 'crawl_status' combines a verb with a noun, while others are single verbs, introducing minor inconsistency.
With 4 tools, the set covers the essential operations of a web crawling service without unnecessary bloat or gaps.
The tools cover core crawling workflows: initiate, monitor, map, and scrape. Missing features like canceling a crawl or listing historical jobs are minor omissions.