This server sends web searches, URLs, scraping targets, browser actions, package names, and dataset requests to Bright Data APIs., Review website terms, robots policies, rate limits, jurisdictional requirements, and internal scraping policies before automating collection., `PRO_MODE`, browser automation groups, data-product groups, and batch tools can increase cost, request volume, and operational impact., The server can create or use Bright Data zones through API calls; review account permissions and zone settings before running it with broad API tokens., Use `RATE_LIMIT`, group selection, and explicit tool allowlists to keep agent-driven browsing and scraping bounded.
Privacy notes
Bright Data API tokens must stay in environment variables or secret managers and should never be committed to MCP configuration files., Queries, URLs, package names, web pages, scraping outputs, dataset filters, and browser activity may be visible to Bright Data, the MCP client, and the model provider., Public web data can still contain personal data, copyrighted content, customer information, or contractual restrictions., Tool outputs can include scraped page text, search results, social or ecommerce dataset fields, package metadata, and browser screenshots depending on enabled tools.
Author
Bright Data
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
5 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, network access, third-party handling.
4 areas
SafetyNetwork accessThis server sends web searches, URLs, scraping targets, browser actions, package names, and dataset requests to Bright Data APIs.
SafetyGeneralReview website terms, robots policies, rate limits, jurisdictional requirements, and internal scraping policies before automating collection.
SafetyNetwork access`PRO_MODE`, browser automation groups, data-product groups, and batch tools can increase cost, request volume, and operational impact.
SafetyCredentials & tokensThe server can create or use Bright Data zones through API calls; review account permissions and zone settings before running it with broad API tokens.
SafetyGeneralUse `RATE_LIMIT`, group selection, and explicit tool allowlists to keep agent-driven browsing and scraping bounded.
PrivacyCredentials & tokensBright Data API tokens must stay in environment variables or secret managers and should never be committed to MCP configuration files.
PrivacyThird-party handlingQueries, URLs, package names, web pages, scraping outputs, dataset filters, and browser activity may be visible to Bright Data, the MCP client, and the model provider.
PrivacyGeneralPublic web data can still contain personal data, copyrighted content, customer information, or contractual restrictions.
PrivacyGeneralTool outputs can include scraped page text, search results, social or ecommerce dataset fields, package metadata, and browser screenshots depending on enabled tools.
Disclosure: Uses Bright Data services, which require an account and may include free-tier, pay-as-you-go, or other plan-specific limits and charges.
Safety notes
This server sends web searches, URLs, scraping targets, browser actions, package names, and dataset requests to Bright Data APIs.
Review website terms, robots policies, rate limits, jurisdictional requirements, and internal scraping policies before automating collection.
`PRO_MODE`, browser automation groups, data-product groups, and batch tools can increase cost, request volume, and operational impact.
The server can create or use Bright Data zones through API calls; review account permissions and zone settings before running it with broad API tokens.
Use `RATE_LIMIT`, group selection, and explicit tool allowlists to keep agent-driven browsing and scraping bounded.
Privacy notes
Bright Data API tokens must stay in environment variables or secret managers and should never be committed to MCP configuration files.
Queries, URLs, package names, web pages, scraping outputs, dataset filters, and browser activity may be visible to Bright Data, the MCP client, and the model provider.
Public web data can still contain personal data, copyrighted content, customer information, or contractual restrictions.
Tool outputs can include scraped page text, search results, social or ecommerce dataset fields, package metadata, and browser screenshots depending on enabled tools.
Prerequisites
Node.js and npx available to the MCP client runtime.
Bright Data account and API token stored as `API_TOKEN`.
Review of Bright Data plan limits, free-tier scope, paid modes, and data-product terms.
A decision about whether to use default rapid tools, `PRO_MODE`, `GROUPS`, or explicit `TOOLS`.
Authorization to search, scrape, automate, or retrieve the target public web data.
Schema details
Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Tool listing metadata
Disclosure
Uses Bright Data services, which require an account and may include free-tier, pay-as-you-go, or other plan-specific limits and charges.
Bright Data Web MCP Server connects Claude and other MCP clients to Bright
Data-backed web access tools. The default server surface includes search and
markdown scraping tools, while optional groups enable browser automation,
ecommerce, social, finance, business, app store, travel, research, GEO, and code
package-data workflows.
The package is published as @brightdata/mcp and runs as a stdio MCP server
with API_TOKEN configured. The upstream server.json documents the required
API token and optional environment variables for zones, pro mode, tool groups,
tool allowlists, polling timeout, request timeout, retries, and rate limiting.
These sources were reviewed on 2026-06-05. Prefer the live repository,
README, package metadata, server source, tool group definitions, server manifest,
license, NPM registry metadata, and Bright Data documentation for current
package versions, API-token requirements, tool groups, plan details, pricing,
and usage limits.
Features
Search Google, Bing, or Yandex through a Bright Data-backed search tool.
Scrape single pages as markdown and run batch scraping when enabled.
Enable browser automation tools for navigation, snapshots, screenshots, clicks, form filling, scrolling, network requests, text, and HTML extraction.
Enable higher-impact groups only after reviewing Bright Data plan terms, request
costs, and the target websites or datasets.
Use Cases
Ask Claude to retrieve current search results for a research topic.
Scrape a public webpage as markdown for summarization or extraction.
Check npm or PyPI package metadata without leaving a coding workflow.
Compare public ecommerce listings or travel data when permitted by policy and plan terms.
Run browser automation against public pages through a Bright Data-backed browser group.
Monitor public brand visibility outputs from supported LLM insight tools.
Safety and Privacy
Bright Data Web MCP Server gives an agent access to live web collection and
dataset APIs. Keep scraping and browser automation within legal, contractual,
and organizational policy boundaries, especially for sites with personal data,
authentication gates, rate limits, or anti-abuse controls.
Use the smallest tool group that fits the task. The base search and markdown
scraping tools have a different cost and risk profile than browser automation,
data-product, social, or batch tools. Keep API_TOKEN and any account-specific
zone configuration out of repositories, and add local rate limits before letting
agents perform open-ended browsing or scraping.
Duplicate Check
No brightdata/brightdata-mcp, @brightdata/mcp, Bright Data Web MCP, or
matching source URL was found in content/mcp.
Show that Bright Data Web MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/bright-data-web-mcp-server)
How it compares
Bright Data Web MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
Official Apify MCP server for connecting Claude to Apify Actors, Actor runs, datasets, key-value stores, and Apify documentation through hosted Streamable HTTP or local stdio transports.
No-key multi-engine MCP server, CLI, and local daemon for web search and public web content retrieval across engines such as Bing, DuckDuckGo, Brave, Exa, Baidu, CSDN, Juejin, Startpage, and Sogou.
✓This server sends web searches, URLs, scraping targets, browser actions, package names, and dataset requests to Bright Data APIs.
Review website terms, robots policies, rate limits, jurisdictional requirements, and internal scraping policies before automating collection.
`PRO_MODE`, browser automation groups, data-product groups, and batch tools can increase cost, request volume, and operational impact.
The server can create or use Bright Data zones through API calls; review account permissions and zone settings before running it with broad API tokens.
Use `RATE_LIMIT`, group selection, and explicit tool allowlists to keep agent-driven browsing and scraping bounded.
✓AgentQL MCP exposes one tool, `extract-web-data`, that sends a target URL and natural-language extraction prompt to the AgentQL API.
The tool is intended for public webpages; do not use it to bypass access controls, scrape private pages, evade paywalls, or extract data where automated collection is prohibited.
Web extraction can still trigger target-site rate limits, legal restrictions, robots guidance, or terms-of-service concerns.
The source implementation uses AgentQL's query-data endpoint with fast mode, no screenshot capture, no scroll-to-bottom behavior, and no local browser cookies.
Treat extracted output as untrusted web data that may include errors, stale content, ads, tracking text, or prompt-injection attempts.
✓Apify MCP can run Apify Actors that browse, scrape, crawl, automate websites, call third-party services, and produce billable Actor runs.
The hosted server supports OAuth and bearer-token authentication; local stdio uses APIFY_TOKEN in the MCP client environment.
Actor tools can access external websites and may trigger anti-abuse systems, platform-policy violations, rate limits, or paid usage.
The server exposes run, dataset, key-value store, and abort tools when Actor workflows are enabled.
Agentic payments can fund Actor runs through x402 USDC on Base or Skyfire PAY tokens, so spending limits and human approval should be enforced outside the model.
Telemetry is enabled by default for tool calls, and the stdio transport uses Sentry for error tracking unless telemetry is opted out.
✓open-webSearch can send search queries to multiple public engines and fetch public web pages, GitHub READMEs, CSDN articles, Juejin articles, and other supported targets.
Search and fetch results can be incomplete, stale, rate-limited, blocked, region-dependent, or affected by search-engine ranking and scraping protections.
Respect each target site's terms and robots expectations; do not use the server for abusive scraping, credentialed browsing, paywall bypass, or personal-data harvesting.
The optional local daemon exposes HTTP endpoints for local tooling; keep it bound to trusted local interfaces and do not treat it as a public internet API.
Proxy settings, Playwright WebSocket/CDP endpoints, and reused browser sessions can route traffic or cookies through external systems; configure them deliberately.
Leave TLS verification enabled unless a specific target has a broken certificate chain and the risk has been accepted.
Privacy notes
✓Bright Data API tokens must stay in environment variables or secret managers and should never be committed to MCP configuration files.
Queries, URLs, package names, web pages, scraping outputs, dataset filters, and browser activity may be visible to Bright Data, the MCP client, and the model provider.
Public web data can still contain personal data, copyrighted content, customer information, or contractual restrictions.
Tool outputs can include scraped page text, search results, social or ecommerce dataset fields, package metadata, and browser screenshots depending on enabled tools.
✓Target URLs, extraction prompts, API key-authenticated requests, and extracted structured data are sent to AgentQL's API.
Extracted data can include personal data, copyrighted content, customer information, job postings, prices, social content, or other third-party material.
AGENTQL_API_KEY should stay out of prompts, issues, logs, screenshots, and committed configuration files.
Claude transcripts and downstream reports may retain extracted data, so avoid collecting information that is not approved for the model session.
✓Actor inputs and requests are sent to the Apify API for execution, and returned datasets or key-value store records can contain scraped personal data, customer records, credentials, contact details, private URLs, or regulated information.
APIFY_TOKEN, OAuth tokens, Skyfire API keys, wallet private keys, payment IDs, dataset IDs, key-value store keys, and Actor run IDs should not be pasted into prompts, issues, logs, screenshots, or committed files.
Search, maps, social, ecommerce, and browser Actors can collect third-party content that may be subject to site terms, privacy law, copyright, or data-retention obligations.
Telemetry and Sentry error tracking should be reviewed before using the local stdio server with sensitive prompts, Actor inputs, or operational data.
✓Search queries, fetched URLs, result titles, snippets, article content, proxy URLs, browser endpoints, and fetched page text can be exposed to MCP clients, logs, and model context.
Live search engines and fetched websites may observe queries, IP address, proxy exit, browser fingerprints, cookies, timing, and request headers.
Playwright fallback or CDP reuse can expose browser state, existing cookies, logged-in sessions, or verification state to fetched pages.
The project includes public URL validation and private-network target protections, but operators should still avoid fetching internal, secret, or customer-specific URLs.
Redact sensitive search terms and downloaded page content before sharing transcripts or logs.
Prerequisites
Node.js and npx available to the MCP client runtime.
Bright Data account and API token stored as `API_TOKEN`.
Review of Bright Data plan limits, free-tier scope, paid modes, and data-product terms.
A decision about whether to use default rapid tools, `PRO_MODE`, `GROUPS`, or explicit `TOOLS`.
Node.js and npx available to the MCP client runtime.
AgentQL API key from the AgentQL developer portal.
Approved list of public webpages or domains Claude may query.
Review of target site terms, robots guidance, rate limits, and data-use rules before extraction.
Node.js 22 or newer available in the MCP client runtime for local stdio usage.
Apify account, OAuth session, API token, x402 wallet, or Skyfire payment setup depending on the chosen transport and payment mode.
Explicit tool selection for production use, because the default tool configuration may change in future versions.
Team approval policy for Actor runs, paid scraping workflows, agentic payments, dataset access, and aborting active runs.
Node.js 18 or newer for the published npm package.
Review of search-engine terms, scraping limits, rate limits, and allowed use for the target websites.
Optional proxy configuration only when live search or fetch traffic must route through an approved proxy.
Optional Playwright or browser endpoint setup only when request-based search/fetch is insufficient.