Bright Data MCP Server: What You Install and What It Costs
What the Bright Data MCP server puts in your agent, how to connect it to Claude Code, what the free tier covers, and a pay-per-call way to read web pages.

Read any web page as Markdown from your agent without wiring up a server first. Paste this into your agent:
Set up https://monid.ai/SKILL.md, and then use Monid to read https://example.com as Markdown and give me the page title and the text.
One prompt reads a page with no scraping server to run. 1 min setup · 3-7 hrs saved.
You searched for the Bright Data MCP server, which means your agent needs live web data and you want to know what you are signing up for: the tools, the token, the free tier and what happens when it runs out. This guide reads Bright Data's own repository for those answers, then shows a second route that bills per call and needs no vendor account, with a page read we ran live on 2026-10-16. It runs through Monid, the OpenRouter for agent tools: one key, one balance, every tool priced per call.
What is the easiest way to give an agent web data through an MCP server?
Monid. Install it once, add a key, and your agent searches a catalogue of web tools at run time, reads the schema and price of the one it wants, and calls it, with no server to host and no vendor account to open first.
- Pay per call. A page read is billed at $0.002533 per call (Verified 2026-10-16 on the agents tools page). Buy calls as you need them: no monthly plan and no minimum top-up. Discovery and inspection are free; only a run bills.
- One install, every tool. The same key and the same balance reach web scraping, search and every other endpoint on Monid. A new source is another call on the same balance, not another token to create.
- Lives inside your agent. Install the CLI, add your key, run the prompt above, and the tools are there whenever the agent needs them, on demand, with nothing to keep running. Your agent reads
SKILL.mdand learns the rest, so setup is about a minute.
Bright Data does ship an official MCP server, and the next two sections say what it contains and what it costs. Monid is the easier route when you want web access without opening a vendor account first, and when you pay for what you run instead of holding an allowance.
What does the Bright Data MCP server install, and how do you connect it?
It installs a set of tools that wrap Bright Data's search, unblocking, scraping and remote browser infrastructure. The repository README, which we read on 2026-10-16, says the server exposes 32 tools. Four groups make up the bulk of them.
| Group | What it holds | Tools |
|---|---|---|
scrapers | Search for and run one of the pre-built Web Scraper API scrapers (Amazon, LinkedIn, TikTok, npm and others) | 6 |
browser | Remote browser automation | 14 |
geo | ChatGPT and Perplexity response collection | 2 |
advanced_scraping | Batch tools, HTML scraping, AI extraction, session stats | 5 |
search_engine, scrape_as_markdown and discover are part of every group. With no group or tool setting, all 32 load. The README states the reason for groups itself: fewer tools means less context for your agent to process.
Which route do you pick, hosted or local?
Two routes are documented. The hosted server is one URL with your token as a query parameter, and the local one is a process started with npx:
https://mcp.brightdata.com/mcp?token=YOUR_API_TOKEN_HERE
API_TOKEN=<your-api-token-here> npx @brightdata/mcp
The hosted route needs no process on your machine. The local route keeps the token in an environment variable. The capabilities are the same either way.
How do you add it to Claude Code?
One command, copied from the README:
claude mcp add --transport http brightdata "https://mcp.brightdata.com/mcp?token=YOUR_API_TOKEN"
The token comes from your Bright Data account settings, so an account is a prerequisite on both routes.
To load only some tools, add groups=scrapers,browser to the hosted URL, or set GROUPS="scrapers,browser" in the environment of the local process. TOOLS picks individual tools by name. Both are the README's own settings.
📖 See also MCP vs API for AI agents
How much does the Bright Data MCP server cost, and is it free?
It has a free tier, and past it the price is per result or per gigabyte. The README states 5,000 free requests a month, renewing on the first of each month, with no credit card required to start. Unused requests do not roll over, and on a team account the allowance is shared across all users.
What does the free tier include?
It covers fetching a page as Markdown, the pre-built scrapers, web search on Google, Bing and Yandex, unblocking, browser automation and geo-targeting.
What does it cost past the free tier?
The README gives pay-as-you-go rates, read and Verified 2026-10-16:
| Search, scrape and extract | Browser navigation | |
|---|---|---|
| Pay as you go (Verified 2026-10-16) | $1.50 per 1,000 results | $8 per GB |
Three details matter. When the free requests run out, requests stop unless you have deposited funds. A credit card is a verification step, and you are charged only if the free tier is exhausted and you hold a deposited balance. And a spend cap can be set in the control panel so pay-as-you-go usage stays inside a budget.
For one developer prototyping, 5,000 requests a month covers a lot of agent activity, and the free tier is the right place to start. The questions that come after it are different: what happens in the month you need 50,000 requests, and what you do on a day you want a source the 32 tools do not cover.
How do you read a web page without a Bright Data account?
Call a page-to-Markdown endpoint through Monid. The endpoint is /web/scrape/markdown from the provider context.dev. It takes a URL and returns the page as Markdown, and the price note on monid inspect says JavaScript rendering, anti-bot handling and premium proxies are included and that failed or blocked requests are not billed.
| Route | What you get | Cost shape | Fits |
|---|---|---|---|
| Bright Data MCP free tier | 32 tools, 5,000 requests a month | Free, then per 1,000 results | One developer on known sources |
| Run your own fetcher | Whatever your code handles | Your hours | A fixed list of easy sites |
| Another vendor's scraping server | That vendor's tools | Their plan | When you already hold their account |
| Monid page read | One call per URL, Markdown and metadata | Pay per call, buy flexibly | Agents that meet new sites at run time |
Monid fits an agent that does not know its sources in advance: the catalogue is searched when the job arrives, and you pay for the pages you read and nothing between runs.
For agents
Grab an API key at app.monid.ai, then paste this to your agent and hand it the key:
set up https://monid.ai/SKILL.md
It learns the whole discover, inspect, run workflow itself. More in the agent quickstart.
For humans
npm install -g @monid-ai/cli
monid keys add -k <your-api-key> -l main
Step 1. Search the catalogue
Discovery is free and not tied to a provider.
monid discover -q "scrape a product page into markdown"
On 2026-10-16 this returned five rows, each with a provider, endpoint, description, billing shape, price and run-time estimate: three MrScraper platform endpoints (Amazon, TikTok Shop and Shein product pages), MrScraper's generic /scrape/markdown, and context.dev/web/scrape/markdown. The prices ranged from $0.001 to $0.05 (Verified 2026-10-16) and the billing shapes mixed per call and per result, which is the reason to read a row before running it.
Step 2. Inspect, then run
Inspecting is free and returns the exact input schema and the current price.
monid inspect -p context.dev -e /web/scrape/markdown
monid run -p context.dev -e /web/scrape/markdown -w \
--query '{"url": "https://example.com/product/123", "useMainContentOnly": true}'
The endpoint is a GET, so the input goes in --query. A search endpoint on the same provider is a POST and takes -i '{...}' with a JSON body instead.
Give this to your agent![]()
Set up https://monid.ai/SKILL.md, and then use Monid to find an endpoint that can read this product page, check its schema and price first, then run it and give me the title and price as JSON.📖 See also Web scraping tools: which kind to use
What does a page read return?
A page read returns the Markdown plus a metadata block, in one JSON object. We ran /web/scrape/markdown twice on 2026-10-16 against https://example.com with useMainContentOnly set to true, so the fields below are what came back.
{ "success": true,
"markdown": "This domain is for use in documentation examples ...",
"contentLength": 1342,
"url": "https://example.com",
"metadata": { "sourceUrl": "https://example.com", "finalUrl": "https://example.com/",
"title": "Example Domain", "language": "en", "favicon": "data:,",
"additionalMeta": { "charset": "utf-8", "viewport": "width=device-width,initial-scale=1" } },
"cache_metadata": { "status": "hit", "age_ms": 750551 },
"finalDOMState": "loaded",
"request_id": "c8c78281-da48-4dec-b700-0612cc7ef4eb" }
The markdown field is the page text, 1,342 characters here, and example.com publishes the same notice in six languages, so all six came back in order with the "Learn more" link at the end. metadata carries the title, the language, the URL you asked for and the URL it ended on after redirects. cache_metadata says whether the result came from a cache, and finalDOMState says the page finished loading.
The schema also lists link and image options, iframe rendering, an extra wait and a proxy country; we ran only the options in the call above.
What you can build on it:
- A reader tool for an agent. Give the agent a URL, get clean text back, and let it answer from the text. A live web data MCP server for agents covers wiring that into Claude Code, Codex or ChatGPT.
- A search-then-read loop. Search first, then read only the results worth the extra call. Search comes from
context.dev/web/search, priced in the table below.
What goes wrong when an agent loads a big tool list or loops on a page?
Three things, two from the Bright Data side as documented and one from our runs.
Why do tool definitions matter before the agent does anything?
Because an MCP server advertises its tools to the model as text, and the model reads that text to know what it can call. The README for this server tells you to load groups so you only carry what you need, which is the same point in the vendor's own words. If your agent uses only search and a page read, groups or TOOLS keeps the other tools out of the window. Running two or three servers side by side adds their lists together.
Why does a free tier that stops matter for an unattended agent?
The README says requests stop when the free allowance is used up and no funds are deposited. For a scheduled agent that is a failure on the first of an unlucky month, not a bill. Decide in advance whether the job should stop, or whether you deposit funds and set the spend cap.
Why did a cached read cost the same as a fresh one?
Because the price is per call, not per fetch. Our first run on example.com came back with cache_metadata status hit and an age_ms of 750,551, meaning the page had been fetched about 12.5 minutes earlier and the result was reused. The second run set maxAgeMs to 0 and came back as a miss with age_ms 0. Both billed one unit, 2,533 micro-dollars, which is $0.002533 each (Verified 2026-10-16), so the two calls cost $0.005066 together (Verified 2026-10-16). The default cache window is one day. A read of a page that changes by the hour needs maxAgeMs set low, and a read of a stable page does not need to pay for a fresh fetch you will not use, so decide per source.
The calls took about 1.1 seconds for the cached result and about 2.3 seconds for the fresh one. The median run time on monid inspect is about 4.1 seconds and the 95th percentile about 19, so budget for the slow end on heavy pages.
Which endpoint should I use for which job?
| Endpoint | What it does | Input | Billing | Price (Verified 2026-10-16) |
|---|---|---|---|---|
context.dev/web/scrape/markdown | One URL to Markdown with metadata | url | Per call | $0.002533 |
context.dev/web/search | Ranked results for a query | query, numResults (10 to 100) | Per result | $0.000253 |
context.dev/web/crawl | Markdown for every page found from a start URL | url, maxPages (up to 500) | Per result | $0.002533 |
Prices Verified 2026-10-16 with monid inspect. The first row is the one we ran. The other two bill per result and hold funds for the number you request, since numResults and maxPages size the hold, so set those small before you loop, and read the charge on a small run first. We inspected search and crawl and did not run them.
📖 See also Crawl4AI and when to run your own crawler
When is another route a better fit?
Your volume fits the free tier. If 5,000 requests a month covers the job, Bright Data's MCP server costs nothing and its token is the only setup.
You need their pre-built scrapers. The README says six tools find and run any of over 1,200 pre-built scrapers across e-commerce, social, business, finance and travel sites. If your agent lives on Amazon and LinkedIn, that structured JSON is the product you want, and a generic page read returns Markdown to parse instead.
You need browser automation. The server has 14 remote-browser tools, billed per gigabyte. A page-to-Markdown call does not click, scroll or log in, and browser automation without an API covers that job.
You want one vendor. One account, one token, one invoice. A catalogue that spans many providers is a different conversation, even with a single balance.
And the disclosure: you are reading Monid's blog, and we resell the context.dev endpoints above. If your agent's tools are known in advance and fit the free tier, install the server that has them.
Conclusion
The quickest way to give an agent a web page without a vendor account is one call through Monid: $0.002533 a page (Verified 2026-10-16), one key for this and every other tool, about a minute to set up and ready inside your agent whenever you need it. The Bright Data MCP server is the right install when your agent works on sources it supports and fits the 5,000 free requests a month.
Two things matter more than which you pick. Load only the tools the job needs, whichever server you use, because every tool definition is text the model reads. And know what your agent does when the allowance ends, whether that is a stop, a bill, or a cap you set.
How we estimated the time saved: opening a vendor account and creating a token takes 30 to 60 minutes per vendor, choosing among a long tool list and setting groups takes 1 to 2 hours, and writing your own fetch layer that renders pages and handles blocking takes 2 to 4 hours. That is 3 to 7 hours. The 1 minute is the install, key and first call once you already have a Monid key.
Free next step: run monid discover -q "scrape a product page into markdown", monid inspect -p context.dev -e /web/scrape/markdown, then read one page you know well and compare the Markdown with the page. Start at monid.ai.
FAQ
Is the Bright Data MCP server free?
It has a free tier of 5,000 requests a month, renewing on the first of each month, with no credit card required to start. Past it, the README lists $1.50 per 1,000 results for search, scrape and extract, and $8 per GB for browser navigation (Verified 2026-10-16), with a spend cap you can set in the control panel.
How do I get a Bright Data MCP API key?
Create a Bright Data account and take the API token from your account settings. The same token goes in the hosted URL as token= or in the API_TOKEN environment variable of the local npx @brightdata/mcp process.
How do I add the Bright Data MCP server to Claude Code?
Run claude mcp add --transport http brightdata "https://mcp.brightdata.com/mcp?token=YOUR_API_TOKEN" with your token in place. Add groups=scrapers,browser to the URL if you want to load only some tools.
What is an alternative to the Bright Data MCP server?
Any other web data server fits, and so does a catalogue your agent searches at run time. With Monid the agent reads a page (see the tools page) for $0.002533 per call (Verified 2026-10-16), with no monthly plan and no minimum top-up, and with no vendor account.
Can I run Bright Data MCP alongside other MCP servers?
Yes. Each connected server advertises its tools to the model, so the lists add up. Connect only the servers an agent needs and use groups or a tool list to trim each one.
Published August 2026.

