WEB EXTRACTION AND AUTOMATION / Bright Data
Bright Data MCP Server
Search-engine results, page scraping, pre-built structured-data scrapers and a remote browser through Bright Data's proxy infrastructure, from a hosted URL or a local npx package.
“The Bright Data MCP server gives AI agents real-time access to public web data.”
01 / THE REASONING
Why this made the selection.
- Published in Bright Data's own repository; package.json at this commit names @brightdata/mcp version 3.0.0 with license MIT, matching the LICENSE (MIT, Copyright (c) 2025 Bright Data).
- The README documents a content gate, on by default, that asks the user before returning scraped content that reads like instructions to change the MCP configuration.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- README.md at 39cc2dcd9937512e22c369b81bad760333e2be61
- LICENSE at the same commit
- package.json at the same commit
Our findings
- The GROUPS and TOOLS environment variables, or groups= and tools= on the hosted URL, restrict which of the README's 32 tools are exposed.
- In the README's environment-variable table RATE_LIMIT defaults to unlimited and BASE_MAX_RETRIES to 0.
- Every request is routed through Bright Data's unblocking infrastructure, which the README says handles bot detection, CAPTCHAs and proxy rotation.
Not established by this review
- npx launch
- The hosted endpoint
- Any scrape, search or browser session
- The content gate
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
npx @brightdata/mcp Copying does not execute this command. It may retrieve a newer version than the reviewed source.
- The README names the line above as the local instance; register it in the client with API_TOKEN in env. It was not run.
- Set GROUPS or TOOLS to expose only the tools you need. Do not commit the token.
Before you start
- Node.js with npx
- A Bright Data API token
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"Bright Data": {
"command": "npx",
"args": [
"@brightdata/mcp"
],
"env": {
"API_TOKEN": "your-token-here"
}
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Bright Data MCP README ↗Checked
https://github.com/brightdata/brightdata-mcp/blob/39cc2dcd9937512e22c369b81bad760333e2be61/README.md
Supports: Hosted and local setup, Content gate, Environment variables, Pricing statement
- Bright Data MCP LICENSE ↗Checked
https://github.com/brightdata/brightdata-mcp/blob/39cc2dcd9937512e22c369b81bad760333e2be61/LICENSE
Supports: MIT License, Copyright (c) 2025 Bright Data
https://github.com/brightdata/brightdata-mcp/blob/39cc2dcd9937512e22c369b81bad760333e2be61/package.json
Supports: Package @brightdata/mcp 3.0.0, License MIT