Bright Data Web MCP

io.github.brightdata/brightdata-mcp

Overview

Bright Data's MCP server for live web search, scraping, structured extraction, browser automation, and package or brand visibility workflows.

Website Repository

Documentation

Overview

Bright Data Web MCP gives MCP clients access to live public web data through Bright Data. It supports hosted remote endpoints and a local npm-based stdio server.

Installation

Use one of the hosted Bright Data MCP endpoints, or install the local stdio server with npm through npx @brightdata/mcp. Hosted endpoints require the Bright Data API token as the token query parameter; the local stdio server requires API_TOKEN in the environment.

Targets

Hosted Streamable HTTP: https://mcp.brightdata.com/mcp with a required token query parameter supplied by the user.
Hosted SSE: https://mcp.brightdata.com/sse with a required token query parameter supplied by the user.
Local stdio: run npx @brightdata/mcp and provide API_TOKEN in the transport environment.

Configuration

Required local environment variable: API_TOKEN. Optional local environment variables: PRO_MODE, RATE_LIMIT, WEB_UNLOCKER_ZONE, BROWSER_ZONE, POLLING_TIMEOUT, BASE_TIMEOUT, BASE_MAX_RETRIES, GROUPS, and TOOLS. Hosted endpoint query parameters include token, pro, groups, tools, unlocker, and browser.

Capabilities

Rapid mode is enabled by default for everyday search and web page scraping. Pro mode and tool groups unlock 60+ tools for structured ecommerce, social, business, finance, travel, app store, GEO/LLM visibility, package metadata, advanced scraping, and browser automation workflows.

Limitations

A Bright Data account and API token are required. The free tier is limited to 5,000 monthly requests/credits at the account level. Pro tools and usage beyond the free tier may incur charges. Complex scraping and browser automation can require longer client timeouts, and scraped web content should be treated as untrusted input.

Registry Metadata Note

Repository metadata uses the full upstream URL https://github.com/brightdata/brightdata-mcp. Package-level and source-review metadata mark API_TOKEN as required and secret for local stdio launch because server.js throws when it is unset. RATE_LIMIT is optional: upstream runtime returns no rate-limit config when RATE_LIMIT is unset, so the safe default is empty/no limit even though docs show example values such as 100/1h.