Best MCP Servers for Warp in 2026
Firecrawl, Bright Data, and Crawlora compared as Warp MCP servers — config, tool counts, and which fits which job (plus where Zyte doesn't reach yet).
Warp turned its terminal agent into a standalone CLI this month. One binary now runs inside Ghostty, iTerm2, VS Code, your native OS terminal, or over SSH with no remote install. That's a real expansion of where Warp shows up in a developer's stack, and nobody's published a Warp-specific buyer's guide for web-data MCP servers yet. This one compares what actually connects, with real config, not marketing copy.
Warp's MCP config
Warp reads MCP server definitions from a JSON file at ~/.warp/.mcp.json (global, applies everywhere) or .warp/.mcp.json at your project root (project-scoped, useful for keeping a client's API key out of servers you don't want available in every session). The root key is mcpServers, the same shape Claude Desktop uses, so most existing configs paste in with no changes. Warp also picks up config from a few third-party agent providers directly (~/.claude.json, ~/.codex/config.toml) if you'd rather not maintain a separate file.
You don't have to hand-edit the file, either: Cmd+P / Ctrl+P → "Open MCP Servers", or Settings → Agents → MCP servers, opens a UI that edits the same JSON for you and shows a live connection status per server.
Warp supports two server shapes:
- Command-based (local/CLI):
{ "command": "...", "args": [...], "env": {...}, "working_directory": "..." }: runs a local process, typically vianpx. - Streamable HTTP/SSE (remote):
{ "url": "...", "headers": {...} }: points at a hosted endpoint, with aheadersfield for anAuthorizationbearer token.
What to evaluate
- Generic crawl (any URL → markdown) vs. structured platform data (named sites → JSON).
- Local command-based server vs. a remote HTTP server you don't have to run yourself.
- Tool count and what it actually covers, not just the headline number.
- Pricing model and whether a failed request still gets billed.
The contenders
| Tool | Format | Coverage | Config | Best for |
|---|---|---|---|---|
| Firecrawl MCP | Local MCP server | Scrape/crawl/search/extract any URL | command-based, npx -y firecrawl-mcp, FIRECRAWL_API_KEY in env | Generic crawl-to-markdown for arbitrary sites |
| Bright Data | Local MCP server (60+ tools) | 40+ named platforms + proxy/anti-bot infra | command-based, npx @brightdata/mcp, API_TOKEN in env (PRO_MODE: "true" for the full 60+-tool set) | Anti-bot-hardened extraction at scale |
| Zyte | N/A | N/A | No official Warp integration | Not currently an option here |
| Crawlora | Remote MCP server | 1,398 tools across 155 platform groups | url-based, https://mcp.crawlora.net/mcp, Authorization: Bearer <key> under headers | Structured JSON from named platforms, pay-on-success, nothing to run locally |
Firecrawl MCP: generic crawl-to-markdown
Firecrawl's MCP server exposes scrape, crawl, map, search, extract, and interact tools against any public URL. It doesn't work from a fixed platform catalog. In Warp, add it as a command-based entry: npx -y firecrawl-mcp, with FIRECRAWL_API_KEY under env. Choose it when the job is reading or crawling arbitrary websites, not a fixed set of named sources.
Bright Data: anti-bot scale across 40+ named platforms
Bright Data documented a Warp integration months before the standalone Agent CLI existed. Its guide predates the August spin-out, and the same command-based config (npx @brightdata/mcp, API_TOKEN under env) still applies. Its 60+-tool MCP server covers named e-commerce, social, business, and finance platforms (Rapid mode is the free 4-tool tier; PRO_MODE: "true" unlocks the full set). Choose it when anti-bot reliability on hard, named targets is the actual constraint.
Zyte: not currently available for Warp
Worth stating plainly rather than skipping: Zyte's two Claude-adjacent products (the Claude Code plugin and the GitHub-Copilot-specific Web Scraping Copilot VS Code extension) are each locked to one client, and neither connects to Warp. If your stack is terminal-first, Zyte isn't currently in the running here.
Crawlora: structured JSON across 155 platform groups, nothing to run locally
Crawlora's MCP server connects to Warp as a url-based remote server: point Warp at https://mcp.crawlora.net/mcp with the API key under a headers.Authorization field (Bearer <key>): no npx process to install or keep running, which matters more in a terminal-native tool than in an IDE. 1,398 tools across search, maps, e-commerce, social, finance, travel, jobs, media, app stores, and reviews, normalized JSON, pay-on-success billing, 2,000 free credits/month with no card. Choose it for structured records from named platforms without maintaining a parser or a local process.
How to choose, by job
- You need to crawl or read arbitrary websites for agent context → Firecrawl MCP.
- You need reliable extraction from specific hard, named platforms at scale → Bright Data.
- You need structured JSON from named platforms without running a local process, billed only on success → Crawlora MCP.
- You specifically want Zyte's Scrapy-generation workflow → you'll need Claude Code or GitHub Copilot for now, not Warp.
Add structured web data to Warp
1,398 tools across 155 platform groups, one API key, billed only on success. 2,000 free credits a month, no card.
Sources
Related reading
- Best MCP Servers for JetBrains IDEs in 2026: another client with a recent AI-agent update, same three vendors.
- Best MCP Servers for GitHub Copilot in 2026: the same comparison, Copilot's config shape.
- Best MCP Servers for Windsurf in 2026.
- Best Web Scraping MCP Servers & Skills for Claude Code in 2026.
- Crawlora vs Firecrawl · Crawlora vs Bright Data.
- Give your AI agent live web data with MCP.
Frequently asked questions
What's the best MCP server for web scraping with Warp?
It depends on the job. Firecrawl MCP fits crawling or reading arbitrary websites. Bright Data is built for anti-bot-hardened extraction across 40+ named platforms and had a documented Warp integration months before Warp spun its agent into a standalone CLI. Crawlora fits when you want structured JSON from named platforms without maintaining a parser or running a local process, billed only on success. Zyte does not currently offer a Warp integration.
Where does Warp read its MCP server config from?
A JSON file at ~/.warp/.mcp.json (global) or .warp/.mcp.json (project-scoped), root key mcpServers — the same shape as Claude Desktop. You can also edit it through a UI: Cmd+P / Ctrl+P → "Open MCP Servers", or Settings → Agents → MCP servers.
Does the new standalone Warp Agent CLI use the same MCP config as Warp Terminal?
Warp's own docs describe MCP configuration in terms of the Warp app broadly rather than calling out CLI-exclusive settings, and the Agent CLI is documented as the same multi-model agent built into Warp Terminal — so the same ~/.warp/.mcp.json config is the reasonable expectation, but Warp hasn't published CLI-specific MCP documentation as of this writing. Worth a quick check in your installed version before assuming.
Does Zyte work with Warp?
Not officially. Zyte's Claude Code plugin and its GitHub-Copilot-specific Web Scraping Copilot extension are each locked to one client, and neither connects to Warp.
How do I install Crawlora's MCP server for Warp?
Add a url-based entry to Warp's MCP config pointing at https://mcp.crawlora.net/mcp, with the API key under a headers.Authorization field (Bearer <key>). No local process to install or run. Free tier is 2,000 credits/month, no card.