Bright Data

Publishes agent connectors and official Skills for web access, search, extraction, and browser services backed by Bright Data.

About Bright Data

Bright Data publishes web-data service connectors including its MCP server, CLI, and official Skills. These interfaces connect agents to service products rather than representing a single standalone local scraping library.

Bright Data exposes several web-data paths. Search discovers candidate pages, fetching reads a known URL, browser tools handle interactive pages, and data products supply prepared datasets. The MCP connector makes selected capabilities available to an agent, while the CLI and SDK fit terminal and application workflows.

The organization’s Skills distinguish onboarding, data collection, browsing, and cost checks. Product access and charges need to be considered alongside the chosen interface; a repository’s open-source license does not grant access to every dataset or cloud browser.

Software from Bright Data

Start from the input you have: a search question, known URL, interactive page, or dataset requirement. Each points to a different service choice.

Alternatives to Bright Data Workflows

Compare UncleCode for content crawling and extraction, Steel for browser session infrastructure, Skyvern for reusable business workflows, Lightpanda for a lightweight browser engine. Choose by the browser environment and task result you need.

Frequently Asked Questions

What is the role of the MCP repository?
It connects MCP hosts to Bright Data capabilities. The server code and the remote products it invokes are related but governed by different setup and service conditions.
Are the Skills published by Bright Data?
The verified brightdata/skills repository is under the same organization and contains task instructions for the service ecosystem.
When should I use MCP instead of the CLI?
Use MCP to expose service tools inside an existing agent host. Choose the CLI for command-driven setup or operations supported by its documentation; both need the relevant Bright Data service access.
Does the publisher only provide browser interaction?
No. Search, fetch, structured extraction, and data products serve different jobs. Choose the needed surface before treating a request as interactive browsing.
Does connector licensing cover paid data?
No. The MCP code is MIT, while service use and data purchases have their own conditions. A task request should not silently approve purchases.
Where should login and key setup happen?
Use official onboarding and client settings. Keep credentials in the local configuration rather than in prompts, reports, or shared repository files.

Choose the Right Web-Data Path

A limited sample shows which service surface fits the input and what usage information is available before committing to a larger data job.