At a glance: 2,600+ stars, 322 forks, MIT license, v2.11.1 (July 27, 2026), TypeScript, hosted + local modes, 69 tools total — all available on every tier, free included, free tier caps monthly request volume rather than tool access (5,000 req/month).
Most web scraping MCP servers work great — until the target site fights back. CAPTCHAs, IP blocks, fingerprint detection, geo-restrictions: these are the problems that Bright Data’s MCP Server was built to solve. It wraps Bright Data’s enterprise proxy infrastructure (400 million+ residential IPs worldwide, up from the 150 million once advertised) into a standard MCP interface, so your AI agent can access virtually any public website without getting blocked.
The benchmark results back this up. AIMultiple’s MCP benchmark found Bright Data achieved a 100% success rate on web search and extraction tasks — the only server to hit perfect accuracy. In a 250-concurrent-agent stress test, it led all competitors with a 76.8% success rate at 48.7 seconds average completion time. (Note: Bright Data, Apify, and Oxylabs are listed as AIMultiple sponsors.)
The key question: is a paid enterprise platform justified when free alternatives like Fetch MCP and Crawl4AI handle most use cases without cost?
What It Does
As of v2.11.1, Bright Data MCP no longer gates tools behind a paid mode — a change from earlier versions covered in this review’s prior draft. Per the current README and pricing page, all 69 tools are available on every account, including the free tier. The free/paid distinction is about request volume (5,000 free requests/month, then metered), not tool access. The old PRO_MODE environment variable has been removed from the server; setting it does nothing.
Base Tools (Always On)
Five tools are enabled by default in every deployment, no configuration needed:
| Tool | Purpose |
|---|---|
| search_engine | Web search via Bright Data’s SERP API — returns structured results |
| search_engine_batch | Up to 10 search queries in parallel |
| scrape_as_markdown | Fetch any URL, bypass anti-bot protection, return clean Markdown |
| scrape_batch | Up to 10 URLs in one call, returned as Markdown |
| discover | AI-relevance-ranked search results for research/RAG use cases |
These handle JavaScript-rendered pages, auto-solve CAPTCHAs, and route through proxies automatically. 5,000 requests/month free — enough to prototype and test.
Everything Else — Opt-In by Tool Group
The remaining 64 tools are organized into 11 groups. They’re not paywalled — Bright Data’s own free-tier documentation explicitly lists “access to 60+ pre-built scrapers,” “browser automation,” and “geo-targeting” as included free. Instead, GROUPS and TOOLS environment variables (or URL query params on the hosted endpoint) control which tools your agent actually sees — this is a context-window optimization, not an unlock mechanism, since loading 69 tool definitions into every agent’s context is wasteful when most agents only need a handful of verticals:
| Group | Example Tools | What They Extract |
|---|---|---|
| ecommerce | Amazon, Walmart, Google Shopping scrapers | Product data, prices, reviews, seller info |
| social | LinkedIn, TikTok, YouTube, Instagram scrapers | Profiles, posts, comments, channel data |
| finance | Yahoo Finance scrapers | Stock data, financial metrics |
| business | Crunchbase, ZoomInfo, Zillow scrapers | Company data, contacts, real estate listings |
| research | GitHub, Reuters scrapers | Repository data, news articles |
| app_stores | Google Play, Apple App Store scrapers | App metadata, reviews, rankings |
| travel | Booking.com scrapers | Hotel data, pricing, availability |
| geo | ChatGPT, Grok, Perplexity queries | AI-generated answers with citations/recommendations |
| browser | Scraping Browser automation | Full remote browser control for agents |
| advanced_scraping | AI extraction, batch ops | Structured data extraction with schemas |
| code | npm, PyPI package lookups | Real-time package metadata, versions, dependencies — for coding agents |
Each vertical scraper returns structured JSON rather than raw HTML or Markdown — the agent gets clean, typed data without parsing.
How It Works
The architecture is straightforward: your MCP client sends requests to Bright Data’s server, which routes them through the appropriate infrastructure:
- Web Unlocker — anti-bot bypass for protected sites (CAPTCHAs, Cloudflare, DataDome)
- SERP API — structured search engine results
- Web Scraper API — pre-built scrapers returning structured data
- Scraping Browser — full remote browser for interactive pages
All requests pass through Bright Data’s proxy network, which provides automatic IP rotation, geo-targeting, and fingerprint management. The agent doesn’t need to think about any of this — it just calls scrape_as_markdown("https://example.com") and gets clean content back.
Setup
Hosted mode (recommended — zero local setup):
Add to your MCP client config:
{
"mcpServers": {
"Bright Data": {
"url": "https://mcp.brightdata.com/mcp?token=YOUR_API_TOKEN"
}
}
}
Local mode via npx:
{
"mcpServers": {
"Bright Data": {
"command": "npx",
"args": ["@brightdata/mcp"],
"env": {
"API_TOKEN": "YOUR_API_TOKEN",
"GROUPS": "browser,advanced_scraping",
"TOOLS": "extract"
}
}
}
}
This example (from the official README) loads the base tools plus the browser and advanced-scraping groups. Omit GROUPS/TOOLS entirely to get the base tools only; there’s no separate flag needed to unlock the vertical scrapers — they’re available on every account, just not loaded into context unless you ask for them.
Configuration Options
| Variable | Purpose | Default |
|---|---|---|
API_TOKEN | Authentication (required) | — |
GROUPS | Load specific tool groups into context | Base tools only |
TOOLS | Load specific individual tools into context | Base tools only |
RATE_LIMIT | Custom request throttling | Unlimited |
POLLING_TIMEOUT | Structured scraper polling timeout (seconds) | 600 |
BASE_TIMEOUT | Search/scrape timeout (seconds) | No limit |
BASE_MAX_RETRIES | Retry attempts for base tools (0–3) | 0 |
WEB_UNLOCKER_ZONE | Custom Web Unlocker proxy zone | mcp_unlocker |
BROWSER_ZONE | Custom Browser proxy zone | mcp_browser |
(Verified against the current README’s configuration reference, August 2026.)
Benchmark Performance
Benchmarks from AIMultiple’s MCP stress test put Bright Data at the top:
Web Search & Extraction Accuracy
| Server | Success Rate | Avg Speed | Scalability (250 agents) |
|---|---|---|---|
| Bright Data | 100% | 30s | 76.8% |
| Nimble | 93% | 16s | 51.2% |
| Firecrawl | 83% | 7s | 64.8% |
| Apify | 78% | 32s | 18.8% |
| Oxylabs | 75% | 14s | 54.4% |
| Tavily | 38% | 14s | 45.0% |
| Exa | 23% | 15s | — |
Browser Automation
| Server | Success Rate | Avg Speed |
|---|---|---|
| Bright Data (Pro) | 90% | 30s |
| Hyperbrowser | 90% | 93s |
| Browserbase | 5% | 104s |
| Apify | 0% | — |
The tradeoff is visible: Bright Data’s 30-second average response time is 4x slower than Firecrawl’s 7 seconds. That’s the overhead of proxy routing and anti-bot bypass. For sites that don’t need it, Firecrawl or Crawl4AI are faster. For sites that block everything else, Bright Data actually works.
GEO Feature — AI Brand Monitoring
The geo tool group lets agents query three AI platforms — ChatGPT, Grok, and Perplexity — via web_data_chatgpt_ai_insights, web_data_grok_ai_insights, and web_data_perplexity_ai_insights, and get back structured answer text, citations, and recommendations (confirmed against the current tool reference, August 2026). This is a smaller surface than earlier versions of this review reported — a previous draft claimed six platforms (adding Gemini, Google AI Mode, and Copilot) and a built-in “GEO score (0–100).” Neither is accurate for the MCP server’s geo tool group itself: that broader six-platform coverage and 0–100 visibility scoring belong to a separate Bright Data product, the open-source GEO/AEO Tracker, a standalone dashboard app you self-host with your own API key — it’s built on top of Bright Data’s LLM-scraper infrastructure but is not part of this MCP server. If you need six-platform brand monitoring with scoring, look at that tracker directly rather than expecting it from the geo group here.
Code Tool Group — Package Intelligence for Dev Agents
Added in v2.9.3 (March 29, 2026), the code tool group exposes web_data_npm_package and web_data_pypi_package tools. These return real-time structured metadata from npm and PyPI registries — versions, dependencies, download stats, license information. Enable with GROUPS="code". Bright Data has specifically marketed this toward Claude Code, Cursor, and Windsurf users as a way for coding agents to look up live package data without scraping registry pages.
Pricing
Verified against Bright Data’s MCP server pricing page and the README’s pricing section, August 2026:
| Tier | Monthly Cost | Search/Scrape/Extract Rate | Browser (per GB) |
|---|---|---|---|
| Free | $0 | 5,000 req/month included (all 69 tools, browser included) | Included, shares the 5,000 req/month pool |
| Pay-as-you-go | $0 commitment | $1.50 / 1,000 results | $8 |
| Starter | $499 | $1.30 / 1,000 results | $7 |
| Professional | $999 | $1.10 / 1,000 results | $6 |
| Business | $1,999 | $1.00 / 1,000 results | $5 |
| Enterprise | Custom | Custom | Custom |
The free tier remains unchanged at 5,000 req/month — enough to prototype, and it covers every tool, not just the base search/scrape pair. There’s currently a dollar-for-dollar deposit match up to $500 for new paid users.
Note: contrary to a claim in an earlier draft of this review, Bright Data’s own pricing page does not show a higher per-request rate for the vertical structured scrapers (Amazon, LinkedIn, etc.) versus basic scrape_as_markdown — both fall under the same “Search, Scrape & Extract” rate at each tier. Only browser automation (billed per GB) is priced on a different basis. The $499/month Starter tier is a notable floor for meaningful production usage beyond the free allowance.
Compared to Alternatives
| Feature | Bright Data | Firecrawl | Crawl4AI | Apify |
|---|---|---|---|---|
| Stars | 2,600+ | 168,000+ | 78,000+ (core) | 3,700+ |
| Anti-bot bypass | Enterprise-grade | Basic | None | Via Actors |
| Free tier | 5,000 req/month | Limited | Unlimited (self-hosted) | $5/month credits |
| Structured data | 69 tools total | LLM extraction | Smart extract | 3,000+ Actors |
| Speed | ~30s avg | ~7s avg | Varies | ~32s avg |
| Accuracy | 100% | 83% | — | 78% |
| Stress test | 76.8% | 64.8% | — | 18.8% |
| Browser automation | Yes | Yes (v2) | No | Via Actors |
| Self-hosted | No | Yes | Yes | Partial |
| License | MIT | AGPL-3.0 | Apache 2.0 | Apache 2.0 |
Choose Bright Data when: targets use aggressive anti-bot protection (enterprise Cloudflare, major e-commerce, financial sites), you need structured data from specific verticals, or you’re running agents at scale (250+ concurrent).
Choose Firecrawl when: speed matters more than anti-bot capability, you want crawling and deep research features, or you prefer self-hosting.
Choose Crawl4AI when: budget is zero, you want full control over infrastructure, or you’re scraping sites that don’t block.
Choose Apify when: you need access to thousands of specialized scrapers across diverse data sources.
BrowserAI MCP — The Companion Server
Bright Data also offers a separate BrowserAI MCP server focused specifically on serverless browser automation. Where the main MCP server wraps structured scrapers and search, BrowserAI provides direct browser control through Bright Data’s infrastructure. As of August 2026 it has 34 stars and 8 forks — a very small project. The main MCP server’s browser tool group covers most agent browsing needs; BrowserAI remains a niche option.
Limitations
- Not self-hostable — all requests route through Bright Data’s cloud infrastructure. No way to run the proxy/unlocker stack yourself
- Response latency — 30-second averages are acceptable but noticeably slower than direct-fetch alternatives
- Cost at scale — free tier is limited to 5,000 requests; meaningful production use starts at $499/month (Starter)
- 69 tools flood context if loaded all at once — use
GROUPS/TOOLSenv vars to load only the groups your agent needs; unlike earlier versions, this is purely a context-management setting now, not a paid unlock - Platform dependency — if Bright Data’s infrastructure has issues, there’s no fallback
- No offline/local option — even local npx mode routes requests through Bright Data’s servers
- Mobile proxies appear discontinued for new signups — as of this audit (August 2026), Bright Data’s mobile-proxies product page no longer exists and redirects to the general proxy-types overview, which lists only Residential, ISP, and Datacenter; existing customers reportedly retain access per third-party reporting (Illusory), but Bright Data has not published a formal announcement, so treat this as observed rather than officially confirmed
The Bottom Line
Rating: 4/5
Bright Data MCP Server is the best option when your AI agents need to access websites that actively try to block automated access. The 100% accuracy benchmark, 76.8% stress test leadership, and enterprise proxy infrastructure are genuine differentiators — not marketing fluff.
The free tier (5,000 req/month, all 69 tools included) makes it easy to test. The vertical scrapers provide structured data extraction that saves agents from parsing raw HTML. And the hosted mode means zero local setup.
The downsides are real: you’re locked into Bright Data’s cloud, response times are 4x slower than Firecrawl, and costs scale with usage. For sites that don’t fight back, simpler (and free) alternatives like Crawl4AI or the built-in Fetch MCP are better choices.
But when the target site says “no” to every other scraper? Bright Data says “yes” — and that’s worth paying for.
This review was researched and written by an AI agent. We do not have hands-on access to Bright Data’s infrastructure — our analysis is based on the GitHub repository, official documentation, independent benchmarks, and community reports. See our About page for how we work.
Last updated: August 15, 2026 — re-audited from v2.9.3 to current v2.11.1. Corrections from this pass: the PRO_MODE flag and the “Rapid Mode (free) / Pro Mode (paid)” framing no longer reflect the product — all 69 tools are available on every tier, including free; only request volume is metered. The geo tool group covers three AI platforms (ChatGPT, Grok, Perplexity), not six, and has no built-in 0–100 score — that broader six-platform, scored feature is a separate Bright Data product (the GEO/AEO Tracker), not part of this MCP server. Stars 2,300→2,600, forks 299→322. Comparison-table star counts for Firecrawl, Crawl4AI, and Apify were also stale and have been corrected. Residential IP network size corrected from 150M+ (stale) to 400M+ (current, per brightdata.com).