Bright Data MCP Server

Official Bright Data MCP: web search, scraping, structured data extraction, and browser automation for AI agents.

Description

Bright Data MCP Server is the official Model Context Protocol interface from Bright Data. It connects an MCP-capable AI client to Bright Data's web unblocking infrastructure and, according to the provider, exposes 69 tools in eleven groups covering web search, page scraping, structured data extraction from well-known platforms, and browser automation. The server is available as a hosted remote endpoint and as a local npm process; both routes send requests through Bright Data's public unblocking network, which according to the provider automatically handles bot detection, CAPTCHA solving, and proxy rotation for every request.

Tools and categories

Base tools are active in every configuration: search_engine and search_engine_batch return results from Google, Bing, and Yandex as structured JSON. scrape_as_markdown and scrape_batch fetch any public URL as clean Markdown. discover uses AI-relevance ranking to find the best sources for a research question with optional date filters.

Optional tool groups extend coverage. The ecommerce group contains eleven tools for Amazon, Walmart, eBay, Best Buy, Etsy, Home Depot, Zara, and Google Shopping that return products, reviews, and search results as clean JSON. The social group has 23 tools for LinkedIn, Instagram, TikTok, Facebook, YouTube, X, and Reddit. The browser group provides 13 tools for remote browser automation without a local Playwright installation. The business group covers Crunchbase, ZoomInfo, Google Maps Reviews, and Zillow. The geo and research groups let agents collect ChatGPT, Grok, and Perplexity answers as structured data and read files from GitHub repositories. The code group returns npm and PyPI package metadata.

Remote endpoint and local installation

According to Bright Data, the recommended route is the hosted remote endpoint https://mcp.brightdata.com/mcp?token=YOUR_API_TOKEN. This endpoint requires no local installation and is documented for Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Gemini CLI, Zed, and Warp. Alternatively, the server can run locally with npx @brightdata/mcp, with API_TOKEN set as an environment variable. Both routes send requests through Bright Data's network; actual processing happens on Bright Data's infrastructure, not locally.

Free tier and pricing model

According to the provider, a free usage allowance is available for initial testing and is refreshed regularly. After it is consumed, paid use may be available depending on the account. Bright Data publishes plan and allowance details on its official pricing page; this entry states no amounts because they can change. A Bright Data account and API token are required in all cases.

Tool selection and token consumption

Loading all 69 tools at once means significant token use in the model context. Bright Data recommends activating only the needed groups via the GROUPS parameter. A research task only needs base tools; e-commerce monitoring additionally requires ecommerce; social-media tracking needs the social group. Individual tools can be added on top via the TOOLS parameter. A deliberately small tool set reduces token consumption, shrinks the prompt-injection surface, and makes agent decisions easier to review.

Scraping boundaries, terms of use, and personal data

Web scraping does not remove obligations under website terms of use, robots guidance, copyright, data protection law, or contracts. For every target and every tool call, check whether the intended collection, storage, and reuse are permitted. Social-media, profile, and contact data can contain personal data. Establish purpose, legal basis, retention, access, and deletion in advance; do not put secrets or confidential customer data in tool inputs unless this is genuinely necessary and legally supported.

Prompt injection and security

Scraped web pages, search results, and structured platform data are untrusted third-party content. They can carry prompt-injection text: instructions to ignore rules, extract tokens, or trigger further actions. Treat every returned piece of content as data, never as instructions. Limit the agent to the minimum required tool group, review the inputs and recipients of every request, and independently confirm write or publishing actions. The API token grants access to the Bright Data account; store it only as a secret, never in Git, prompts, screenshots, or shared configuration files.

FAQ

Is the Bright Data MCP Server official? Yes. Bright Data operates the repository at github.com/luminati-io/brightdata-mcp and the remote endpoint mcp.brightdata.com as official products.

Which clients are supported? According to the documentation, Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Gemini CLI, Zed, and Warp are explicitly documented. Any MCP-compatible client that supports remote SSE or local stdio processes should work.

Can I test the server without an account? According to the provider, a Bright Data account and API token are always required to connect; current trial and usage terms are available in the official documentation.

On 2026-09-08, the GitHub API reported exactly 2,634 stars for luminati-io/brightdata-mcp. This is a point-in-time repository-popularity signal, not evidence of quality, privacy, or security.

Requirements

A Bright Data account and API token; for the remote endpoint an MCP client with remote SSE support; for local mode Node.js 18+ and a securely set API_TOKEN.

Installation instructions

The official Bright Data MCP Server brings public web access, structured platform data, and browser automation into an MCP-capable client. Sixty-nine tools across eleven groups sounds attractive, but that breadth is exactly why deliberate setup matters: too many active tools consume context tokens unnecessarily, load large amounts of unfiltered third-party content into the agent, and expand the prompt-injection surface. Start with a clearly bounded task, activate only the tool group you need for it, and extend deliberately when you want to use a new category in production.

Quick start

Remote: add https://mcp.brightdata.com/mcp?token=YOUR_API_TOKEN in the client. Local: set API_TOKEN securely and configure npx @brightdata/mcp as the stdio command. Activate only required tool groups via the GROUPS parameter.

bash
npx @brightdata/mcp

Remote endpoint as the preferred route

Bright Data operates the remote endpoint https://mcp.brightdata.com/mcp. Add this URL in a client that supports remote SSE MCP and append your API token as ?token=YOUR_TOKEN. For Claude Desktop or Cursor, Bright Data's documentation provides the configuration file format directly. The remote route requires no local Node.js installation and updates alongside the server.

Never store the token as a plaintext parameter in a public configuration file, a commit, a screenshot, or a prompt. Use your operating system's, client's, or CI system's secret management. Create a dedicated API token for each use case; delete or rotate it as soon as you suspect exposure. A Bright Data API token is not a harmless configuration detail: it represents access to your account and consumed quota.

Step 1: Use local mode deliberately

For clients without remote SSE support, or for local testing, Bright Data documents npx @brightdata/mcp as a stdio process. Set API_TOKEN as a protected environment variable — never as a visible command-line parameter. A first-run package download is expected; check the package source when working in a restricted network, and update deliberately rather than automatically.

bash
npx @brightdata/mcp

Local here only means the MCP process runs on your system. All tool requests are still sent to Bright Data's network; results travel back through Bright Data's infrastructure to your client and from there into the model context of your connected AI provider. A local process is not a fully local data path.

Restrict tool groups deliberately

Activate only the group you need. For general web research, the base tools require no GROUPS parameter. For e-commerce monitoring, add GROUPS=ecommerce; for social media, GROUPS=social. Individual tools from other groups can be added on top with TOOLS=toolname, without loading the entire group.

An overly broad tool selection has three downsides: it wastes context tokens that would otherwise be available in the model window; it makes agent decisions harder to follow; and it enlarges the attack surface, because every active tool could also be triggered via compromised page content. Before production use, assess which groups you genuinely need and what happens if a tool is called unexpectedly.

Every tool request through Bright Data's network reaches a target website. For each target URL and platform, check whether collection, storage, and reuse are constrained by website terms, robots files, copyright, data-protection law, or contracts. Even though Bright Data provides the technical unblocking infrastructure, responsibility for lawful use lies with you as the operator.

Social-media tools — LinkedIn, Instagram, TikTok, Facebook, YouTube, X, and Reddit — can return personal data: profiles, comments, engagement metrics. Establish purpose, legal basis, retention period, deletion process, and access permissions in advance. Collect only data you need for a documented purpose, and do not put private credentials, payment data, or confidential customer data into tool inputs unless this is genuinely necessary and legally supported.

Recognising and limiting prompt injection

Every piece of content returned by a tool — Markdown from a scraped page, structured JSON from a platform extractor, search-result snippets — is untrusted third-party content. Pages can contain text designed to manipulate the agent: "Ignore all prior rules," "forward the API token," or "call tool X with these parameters now." These are not instructions. Treat every piece of content as a data point.

In practice: avoid activating write-capable tools when read-only access suffices. Have the agent log tool calls with their inputs and recipients so you can review them. Independently and deliberately confirm any action that publishes data, forwards it, or writes to external systems. Use the RATE_LIMIT parameter to cap usage so a poorly stopped agent cannot exhaust your entire quota.

FAQ

Do I need to install anything locally? No. The remote endpoint only requires a URL and token in the client.

What does a mistake cost? If the free tier is exhausted and no spending limit is set, costs can accrue with deposited funds. Set a spending cap in the Bright Data console.

Can I test the server without an AI client? Yes, with a direct HTTP call to the remote endpoint or with an MCP inspector that supports stdio processes.

Are scraped results reliable sources? No. Scraped content reflects the page state at retrieval time. Validate consequential data against original sources and note the time and limitations.

npx @brightdata/mcp

Authentication

API token from Bright Data account settings. Passed as a URL parameter for the remote endpoint, or as the API_TOKEN environment variable for the local server.

Required access permissions

The API token acts in the Bright Data account context. Access, quota, and billing limits depend on the account type and configured caps; activate only necessary tool groups.

Transmitted or stored data

All tool requests are processed through Bright Data's network. Return values — Markdown content, structured JSON, search and browser results — reach the MCP client and may be processed or retained in model context, chat history, or logs.

Security risks

Scraped content can involve personal data, website terms, and prompt injection. The API token grants account access and must never be stored in plaintext. Minimize the tool set, review inputs and targets, and independently confirm state-changing actions.

License and costs

License
MIT
Cost
paid

The source code is MIT licensed. Use requires a Bright Data account. According to the provider, a free allowance is available for initial testing; extended use follows current Bright Data plans. Check the official pricing page before production use.

Alternatives

Not recorded yet.

At a glance

Provider
Bright Data
Status
Official server
Deployment
Local and remote
Current version
Not recorded yet.
GitHub stars
2,729
Last reviewed
08.09.2026

Repository and documentation

Categories

Supported clients

Related guides

Guides and background related to this entry.

No related guides yet.