Bright Data MCP

Web search, page scraping, structured data extraction, and browser automation for AI agents and LLMs over the Model Context Protocol.

Works with AI agents, coding agents, chat assistants, and any MCP-compatible client.

Quick Start • Pricing • Use Cases • Tools • Agent Skills • Docs • Support

Free tier: 5,000 requests per month. No credit card required. Renews monthly.

Overview

The Bright Data MCP server gives AI agents real-time access to public web data. It exposes 30 tools covering:

• Web search — Bing and Google results as structured data
• Page scraping (Fetch API) — any URL as Markdown, text, HTML or JSON-LD. Long pages can be read in parts
• Structured data (Web Scraper API) — clean JSON from 1,200+ pre-built scrapers: Amazon, LinkedIn, Instagram, TikTok, YouTube, X, Reddit, Facebook, Crunchbase, Zillow, npm, PyPI and more, without parsing HTML. Six tools find and run any of them
• Browser automation — navigate, click, type, screenshot, and read pages in a remote browser session
• LLM response collection — send a prompt to ChatGPT or Perplexity and get the answer text back as Markdown

Two deployment options: a hosted remote server (one URL, no installation) or a local instance via npx @brightdata/mcp.

Quick Start

Hosted server — no installation. Add this URL to your MCP client:

https://mcp.brightdata.com/mcp?token=YOUR_API_TOKEN_HERE

Get your API token from your Bright Data account settings. New accounts get 5,000 free requests per month.

Optional URL parameters:

{
  "mcpServers": {
    "Bright Data": {
      "command": "npx",
      "args": ["@brightdata/mcp"],
      "env": {
        "API_TOKEN": "<your-api-token-here>"
      }
    }
  }
}

claude mcp add --transport http brightdata "https://mcp.brightdata.com/mcp?token=YOUR_API_TOKEN"

{
  "mcpServers": {
    "brightdata": {
      "url": "https://mcp.brightdata.com/mcp?token=YOUR_API_TOKEN"
    }
  }
}

{
  "servers": {
    "brightdata": {
      "type": "http",
      "url": "https://mcp.brightdata.com/mcp?token=YOUR_API_TOKEN"
    }
  }
}

{
  "mcpServers": {
    "brightdata": {
      "serverUrl": "https://mcp.brightdata.com/mcp?token=YOUR_API_TOKEN"
    }
  }
}

{
  "mcpServers": {
    "brightdata": {
      "httpUrl": "https://mcp.brightdata.com/mcp?token=YOUR_API_TOKEN"
    }
  }
}

{
  "context_servers": {
    "brightdata": {
      "url": "https://mcp.brightdata.com/mcp?token=YOUR_API_TOKEN"
    }
  }
}

{
  "brightdata": {
    "url": "https://mcp.brightdata.com/mcp?token=YOUR_API_TOKEN"
  }
}

{
  "mcpServers": {
    "Bright Data": {
      "command": "npx",
      "args": ["@brightdata/mcp"],
      "env": {
        "API_TOKEN": "<your-api-token-here>"
      }
    }
  }
}

Pricing and Free Tier

Every account includes a recurring monthly free tier. No credit card or commitment required to start.

5,000 free requests per month, renewing on the 1st of each month. Unused requests don't roll over. For team accounts, the free tier is shared across all users in the account.

What's included free:

• Fetch any webpage and extract as Markdown
• Access to 60+ pre-built scrapers for popular domains
• Web search (Bing, Google)
• Browser automation
• Geo-targeting

Beyond the free tier — pay as you go, no commitment:

• When free requests run out, requests stop. No surprise charges — unless you have deposited funds
• Adding a credit card is a verification step only; you are not charged unless your free tier is exhausted and you have funds deposited
• Set a spend cap in the control panel so pay-as-you-go usage never exceeds your budget

Full pricing, volume plans and enterprise →

Use Cases

Real-time research

Answer questions using live web data instead of training data. Search, then read the sources.

Example prompts: "What's Tesla's current stock price?", "Get today's weather forecast for New York", "Find the most cited sources on EU AI regulation from the last 6 months".

E-commerce intelligence

Read product data as structured JSON: price, availability, rating, review count, seller, images.

Example prompts: "Compare this laptop's price on Amazon vs Walmart vs eBay", "Get the rating and review count for ASIN B0D2Q9397Y", "Is this product in stock?".

Market and competitor analysis

Build competitor profiles from live data: funding, headcount, hiring, customer reviews, pricing pages.

Example prompt: "Analyze Notion as a competitor: pricing, funding, hiring focus, and what customers complain about".

AI agents with reliable web access

Replace built-in fetch and search tools. Pages that need JavaScript or clicks go to the remote browser tools.

Coding agents

Package registry data on demand — no scraping, no stale caches.

Example prompts: "What's the latest version of express on npm?", "Get the README for the langchain-brightdata PyPI package".

GEO and brand visibility

Send a prompt to ChatGPT or Perplexity and get the answer text back as Markdown. Each call sends one prompt.

Example prompt: "Ask ChatGPT and Perplexity 'what is the best proxy provider' and compare how each one ranks us".

Social media monitoring

Structured data from every major platform: profiles, posts, comments, engagement metrics. Each platform has scrapers per data type (LinkedIn profiles, Instagram reels, TikTok comments, ...); find them with search_scrapers and run them with run_scraper.

Example prompt: "Get the last 10 posts from this TikTok profile and summarize the engagement".

Content creation and academic research

Gather source material from many pages at once, filtered by recency and relevance.

Tool Selection: Groups

Tools are organized into groups so you only load what you need. Fewer tools means less context for your agent to process.

• With no GROUPS or TOOLS, all 30 tools are enabled. Setting either one limits the server to those tools only
• GROUPS enables tool bundles. Comma-separated: GROUPS="scrapers,browser" (local) or &groups=scrapers,browser (hosted URL)
• TOOLS adds individual tools on top: TOOLS="scrape_batch,session_stats". On its own, it enables only the tools you list
• Every group also includes search_engine, scrape_as_markdown and ask_brightdata_assistant
• Group ID custom is reserved; use TOOLS for individual picks

Older group IDs (ecommerce, social, business, finance, research, app_stores, travel, code) still work and enable the scrapers tools; social and business also add search_dataset and list_dataset_fields. Old web_data_* names in TOOLS enable the scrapers tools too.

Configuration examples

Local server with browser automation and batch tools:

{
  "mcpServers": {
    "Bright Data": {
      "command": "npx",
      "args": ["@brightdata/mcp"],
      "env": {
        "API_TOKEN": "<your-api-token-here>",
        "GROUPS": "browser,advanced_scraping"
      }
    }
  }
}

Coding agent setup (Claude Code / Cursor / Windsurf) — npm, PyPI and GitHub data through the pre-built scrapers:

{
  "mcpServers": {
    "Bright Data": {
      "command": "npx",
      "args": ["@brightdata/mcp"],
      "env": {
        "API_TOKEN": "<your-api-token-here>",
        "GROUPS": "scrapers"
      }
    }
  }
}

Tools Reference (30 Tools)

Which tool to use

• Known URL, need the content: scrape_as_markdown. Multiple URLs (up to 5): scrape_batch
• Need to find information: search_engine. Multiple queries (up to 5): search_engine_batch
• Structured data from a known platform (Amazon, LinkedIn, TikTok, npm, PyPI, etc.): search_scrapers → get_scraper_details → run_scraper. Returns JSON records. If the run takes longer than 45 seconds, run_scraper returns a snapshot_id: check it with get_scraper_progress, then read the records with get_scraper_results
• Raw HTML: scrape_as_markdown with format: 'html'
• Page cut at 40,000 characters: call scrape_as_markdown again with snapshot_id and start from the result's next field. The rest is read from the saved page at no extra cost
• Page needs JavaScript or interaction (click, type, scroll): scraping_browser_* tools. The scrape tools don't render JavaScript
• How ChatGPT/Perplexity answer a prompt: chatgpt_ai_insights / perplexity_ai_insights
• Question about Bright Data itself (products, zones, errors, setup): ask_brightdata_assistant

Notes on scraper runs:

• Return structured JSON, billed per record returned
• Records with an error field explain inputs that failed, e.g. a URL of the wrong type
• Results can be large. Keep limit_per_input low for discover_by_* methods and run bulk collection in a subagent where your framework supports it, so records don't flood the main context window
• If a run fails, scrape_as_markdown works on the same URL as a fallback

Full tool reference in the docs →

Agent Skills

Bright Data's agent skills teach your agent when and how to use Bright Data. They live at github.com/brightdata/skills. Start with agent-onboarding.

Configuration

Basic setup (local)

{
  "mcpServers": {
    "Bright Data": {
      "command": "npx",
      "args": ["@brightdata/mcp"],
      "env": {
        "API_TOKEN": "your-token-here"
      }
    }
  }
}

Advanced configuration

{
  "mcpServers": {
    "Bright Data": {
      "command": "npx",
      "args": ["@brightdata/mcp"],
      "env": {
        "API_TOKEN": "your-token-here",
        "RATE_LIMIT": "100/1h",
        "SERP_ZONE": "custom_serp",
        "BROWSER_ZONE": "custom_browser"
      }
    }
  }
}

Environment variables

Content gate

scrape_as_markdown, search_engine and their batch variants return whatever a web
page says. If that content contains text that reads like instructions to change your MCP
configuration — register a server, run an npx -y package, edit the MCP config file — the server
pauses and asks you, through your MCP client, before returning it. Approve and the content is
returned unchanged; decline and it is withheld with a short explanation to the assistant. Pages that
do not contain such text are returned exactly as before, with no prompt. For a batch call, only the
matching items are withheld.

Pages that are about MCP configuration (documentation, READMEs) will naturally prompt. Clients that
do not support MCP elicitation get the matching content withheld; set CONTENT_GATE=off if you
accept the risk. While the server waits for your answer it reports progress; clients that do not
extend their tool timeout on progress will cap the wait at their own limit — CONTENT_GATE_TIMEOUT
is the knob on the server side. Browser tools are not covered.

Documentation

Troubleshooting

"command": "/usr/local/bin/node"  // macOS/Linux
"command": "C:\\Program Files\\nodejs\\node.exe"  // Windows

Contributing

• Report bugs
• Suggest features
• Submit PRs

Please follow Bright Data's coding standards.

Support

License

MIT © Bright Data Ltd.