Data as of
Firecrawl MCP Server for VS Code: Setup & Config
Firecrawl MCP connects VS Code to web search, scraping, crawling, and live browser interaction.
Firecrawl MCP Server VS Code configuration
Choose VS Code configuration scope
For Firecrawl MCP Server, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.
Add Firecrawl MCP Server to VS Code
Use the firecrawl-mcp-server entry below in servers. Keep Firecrawl MCP Server's documented stdio connection fields and your other VS Code entries.
Check Firecrawl MCP Server in VS Code
Firecrawl MCP Server: Start in VS Code’s MCP controls; inspect output and trust prompts.
Config file · Workspace: .vscode/mcp.json
{
"servers": {
"firecrawl-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"firecrawl-mcp"
],
"env": {
"FIRECRAWL_API_KEY": "<your Firecrawl API key>"
}
}
}
}Firecrawl in VS Code: stdio checks
- Make npx firecrawl-mcp (Node.js/npm) available in the workspace, container, or remote environment hosting Firecrawl MCP Server. Start through VS Code's MCP controls; inspect output and trust prompts.
- For Firecrawl MCP Server, keep FIRECRAWL_API_KEY out of version control; VS Code documents input variables and secret handling.
- Firecrawl MCP Server uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
- Tools
- firecrawl_scrape, firecrawl_map, firecrawl_search
Firecrawl MCP Server — details. VS Code guide
Frequently asked questions
For Firecrawl MCP Server, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.
VS Code's firecrawl-mcp-server example uses stdio.
Firecrawl MCP Server's VS Code configuration invokes npx firecrawl-mcp (Node.js/npm).
VS Code's Firecrawl MCP Server example references FIRECRAWL_API_KEY. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.
Firecrawl MCP Server's stored list contains 27 tools, including firecrawl_scrape, firecrawl_map, firecrawl_search. Compare those names with VS Code's connected tool list; the stored list is not a live check.