Server facts
Bright Data Web MCP
Project
- Author
- luminati-io
- Repository
- github.com/luminati-io/brightdata-mcp
- Website
- brightdata.com/
- License
- MIT
- Category
- Search & Web Data
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 2,678
- Last commit
- Data as of
Tags
- Browser Automation
- Package Metadata
- Web Scraping
- Web Search
Overview
Bright Data Web MCP connects assistants to web search and extraction services operated by Bright Data. Its base toolkit searches the web, retrieves pages as Markdown, and offers intent-ranked discovery. Batch variants support work across multiple searches or pages. The README positions these capabilities for current research, price monitoring, competitor analysis, and content preparation. Users can connect to a hosted endpoint or run the MCP process locally with an API token, making the same service available to different kinds of MCP clients.
Additional capabilities are organized into selectable groups rather than requiring every tool to be exposed. These include browser control, retail datasets, social content, finance, travel, and business information. A code group supplies npm and PyPI package details, while a GEO group queries ChatGPT, Grok, and Perplexity for brand-related insights. The default Rapid mode has a monthly credit allowance; Pro mode enables the larger toolkit and incurs usage charges. Custom selection narrows the surface through group and tool settings but does not bypass paid eligibility. Browser automation is not part of the free base mode. Configuration also includes request limits, timeouts, and custom zones. Consequently, choosing this server involves both selecting relevant tools and understanding which Bright Data services consume credits for the intended workflow.
Install & configure
Requirements
- Node.js with npx for local execution
- A Bright Data account and API token
- An MCP-compatible client
npx @brightdata/mcpThis configuration uses the local process. A hosted endpoint is also documented. Rapid mode is the default; optional groups and Pro tools can change usage costs.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"brightdata-mcp": {
"command": "npx",
"args": [
"@brightdata/mcp"
],
"env": {
"API_TOKEN": "<your Bright Data API token>"
}
}
}
}Config file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"brightdata-mcp": {
"command": "npx",
"args": [
"@brightdata/mcp"
],
"env": {
"API_TOKEN": "<your Bright Data API token>"
}
}
}
}Config file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
{
"servers": {
"brightdata-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"@brightdata/mcp"
],
"env": {
"API_TOKEN": "<your Bright Data API token>"
}
}
}
}Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"brightdata-mcp": {
"command": "npx",
"args": [
"@brightdata/mcp"
],
"env": {
"API_TOKEN": "<your Bright Data API token>"
}
}
}
}Config file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"brightdata-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"@brightdata/mcp"
],
"env": {
"API_TOKEN": "<your Bright Data API token>"
}
}
}
}Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Tools
Source: repository README. Tool descriptions are a documented snapshot, not a live capability check.
| Tool | What it does |
|---|---|
| search_engine | Search the live web for results suitable for an assistant's research workflow. |
| search_engine_batch | Run multiple web searches as a batch. |
| scrape_as_markdown | Extract a web page into Markdown content. |
| scrape_batch | Retrieve content from multiple pages in one batch workflow. |
| discover | Find web results ranked against the intent of a research query. |
| scrape_as_html | Retrieve HTML through an explicitly selected scraping tool. |
| extract | Use the advanced scraping group for AI-assisted extraction. |
| scraping_browser_snapshot | Inspect the state of a remotely controlled browser. |
| scraping_browser_click_ref | Click a referenced element in the remote browser. |
| scraping_browser_screenshot | Capture an image from the remote browser. |
| web_data_amazon_product | Retrieve structured Amazon product information. |
| web_data_walmart_product | Retrieve structured Walmart product information. |
| web_data_google_shopping | Access Google Shopping dataset information. |
| web_data_linkedin_posts | Retrieve structured LinkedIn post data. |
| web_data_tiktok_posts | Retrieve structured TikTok post data. |
| web_data_youtube_videos | Retrieve structured YouTube video information. |
| web_data_yahoo_finance_business | Access company information from Yahoo Finance. |
| web_data_crunchbase_company | Retrieve Crunchbase company data. |
| web_data_zoominfo_company_profile | Access structured ZoomInfo company profiles. |
| web_data_zillow_properties_listing | Retrieve Zillow property listing data. |
| web_data_github_repository_file | Retrieve repository file data from GitHub. |
| web_data_reuter_news | Access the documented Reuters news dataset tool. |
| web_data_google_play_store | Retrieve Google Play store data. |
| web_data_apple_app_store | Retrieve Apple App Store data. |
| web_data_booking_hotel_listings | Access Booking hotel listing information. |
| web_data_chatgpt_ai_insights | Query ChatGPT for structured AI insights and brand visibility research. |
| web_data_grok_ai_insights | Query Grok for AI insights useful in brand visibility research. |
| web_data_perplexity_ai_insights | Query Perplexity for sourced AI answers and brand visibility research. |
| web_data_npm_package | Look up npm package versions, documentation, and dependency metadata. |
| web_data_pypi_package | Look up Python package versions and project information from PyPI. |
Names, permissions, and defaults can change. Check the current upstream documentation before granting access.
Use cases
- Research current web information and extract readable page content.
- Monitor product details and prices across retail datasets.
- Look up npm or PyPI versions, metadata, and READMEs.
- Compare AI-generated brand mentions across supported LLM services.
Strengths
- Supports hosted access and a documented local npx configuration.
- Tool groups let users limit the capabilities exposed to an assistant.
- Combines search, scraping, structured datasets, and optional browser control.
Limitations
- Requires a Bright Data API token.
- Browser automation and Pro capabilities incur usage charges.
- Requests stop after the free credit pool is exhausted unless funds are available.
Frequently asked questions
Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.