Skip to main content

Building an AI startup?

You might be eligible for our Startup Program. Get fully funded access to the infrastructure you’re reading about right now (up to $20K value).

Modes: Rapid (Free), Pro and 11 tool groups

Bright Data’s MCP server offers two modes to suit different needs:
  •   Rapid (Free) - Quickly scrape search results and unlock any public webpage as clean Markdown.
  •   Pro - Access advanced scraping, structured data from top platforms (Amazon, LinkedIn, X, Instagram, etc.), and full browser automation. Built for dynamic and large-scale use cases.
  • Groups - Pre-configured tool collections for specific use cases including E-commerce, Social Media, Browser Automation, Business Intelligence, Finance, Research, App Stores, Travel, Advanced Scraping, GEO & LLM Visibility, and Code. Each group bundles relevant tools and data feeds for its domain.

To use Pro mode:
  • In Remote MCP, request Pro features by setting &pro=1.
  • In Local MCP, enable Pro features with PRO_MODE=true.
To use Groups:
  • In Remote MCP, request the Groups by setting &groups=<group_name>.
  • In Local MCP, enable Groups with GROUPS=<group_name>.
Rapid (Free) mode is enabled by default and is recommended for everyday browsing and data needs.

Bright Data MCP Tools Reference

How do I search datasets by filter with the Bright Data MCP server?

Use list_dataset_fields and search_dataset to find many records that match your criteria, as opposed to the web_data_* tools, which fetch one record by URL. The search runs directly against the dataset with no snapshot step and returns up to 10 records per call. Under the hood, list_dataset_fields calls the Get dataset metadata endpoint and search_dataset calls the Search dataset endpoint of the Marketplace Dataset API. Three datasets are searchable: The workflow is two calls:
  1. Call list_dataset_fields with a dataset_id. It returns each filterable field’s name, type and description.
  2. Call search_dataset with the same dataset_id and a filter.
A filter is a tree with a maximum nesting depth of three. Each node is either a group, {"operator": "and" | "or", "filters": [...]}, or a leaf, {"name": ..., "operator": ..., "value": ...}. See filter syntax for the full list of leaf operators and their behavior. For example, this filter matches profiles in the United States whose position mentions data engineering:
The response contains hits (the matching records), total_hits and took (search time in milliseconds). To page through more than 10 results, set sort to "default" or a custom sort like [{"timestamp": "asc"}], then pass the response’s search_after cursor into the next call. Set sort to "random" to sample records instead.