Skip to main content
Get structured data out of the Bright Data Scraper API from inside Claude Code, Cursor or Codex. Paste this in:

Read https://docs.brightdata.com/llms.txt, then use the Bright Data Scraper API to scrape https://www.amazon.com/dp/B0FQFB8FMG and show me the title, price and rating.

The agent reads the documentation index, installs what it needs and returns the record. To run the same thing yourself, or to see what it installed, start below.

Get your first Scraper API result

Two commands to structured JSON from the Bright Data Scraper API. Same result as the human quickstart, driven from the terminal.
1

Install and authenticate

bdata login opens a browser to authorize, so you never paste a key. Use bdata login --device over SSH or in any headless environment.If a global install is blocked on your machine, run each command through npx instead:
Keep the -p @brightdata/cli part. npx does not put bdata on your PATH, so every command needs the prefix, and the short npx bdata resolves to an unrelated package on npm rather than the Bright Data CLI.
2

Scrape a page

You should see the product JSON printed. This takes 10 to 30 seconds.
The full record carries 67 fields. Run bdata pipelines list to see every available pipeline type.
Install the agent skills and the agent reaches for these commands itself:
Then ask in plain language instead of typing the CLI:
Prompt

How do I scrape a different site?

Change the pipeline type. The CLI names each one after what it collects, so there is no dataset_id to look up.
For the current set:
Search engines are not pipelines. Use bdata search for Google, Bing and Yandex results, and bdata scrape for any page that has no pre-built scraper. With the skills installed you do not pick the type yourself. Ask for the data and the agent matches the site to a pipeline:
Prompt

What the agent sets up

These are not alternatives. See how they fit together.

Prerequisites

  • A Bright Data account. New accounts get 5,000 free credits every month, no credit card required
  • A coding agent with terminal access: Claude Code, Cursor, Codex or any of the 40+ agents the skills ecosystem supports

How do I give my agent the full documentation?

Point the agent at llms.txt, a structured index of every Bright Data documentation page following the llms.txt standard. Every entry links to the .md version of the page, so the agent reads clean markdown with no HTML to parse.
Prompt
To make it permanent instead of per-prompt, save the index into your project so every session has it:
Two files are published. llms.txt is the index and is the right default for a live agent session. llms-full.txt is the entire documentation in one file, meant for RAG pipelines and long-context injection rather than interactive use.
The token-efficient pattern for agents: load llms.txt to see what exists, identify the relevant page, then fetch that page’s .md URL for the detail. Append .md to any documentation URL to get the markdown, for example /products/mcp-server/overview.md.
Prefer to have the agent query the docs live instead of loading a file? The Docs MCP exposes this documentation as searchable MCP resources, so the agent retrieves pages inside its own reasoning loop. It is a separate server from the Bright Data MCP below: the Docs MCP reads documentation, the Bright Data MCP reaches the live web. Building a retrieval pipeline rather than a live agent session? Use llms-full.txt, which is the complete documentation as one markdown file:
llms-full.txt is large. For a live agent session, load llms.txt first and fetch individual .md pages on demand instead. It uses far fewer tokens.

How do I install Bright Data skills?

Skills are reusable instruction sets defined in SKILL.md files that give your agent embedded Bright Data API knowledge and the commands to act on it through the Bright Data CLI. One command installs them and auto-detects which agents you have:
The skills call bdata directly, so the global install from step 1 is what makes them work. Without bdata on your PATH the skills’ command -v bdata check fails. Confirm the install landed:
Each installed skill prints on its own line with its path and the agents it was linked into:
An empty list means the install did not take. Re-run npx skills add brightdata/skills and answer the scope prompt. The bundle covers search, scraping, structured extraction, the SDKs, proxies, Scraper Studio and MCP orchestration. The ones you will reach for first: Run npx skills add brightdata/skills --list for the current set. Once installed, the agent invokes them directly:

Install into a specific agent

Skills land in .claude/skills/ in your project, or ~/.claude/skills/ with -g. Claude Code discovers them on the next session. Verify with npx skills list -a claude-code.
Add -g to any command to install globally across projects.

Manage installed skills

Skills are part of the open agent skills ecosystem and work across 40+ coding agents. The source, including each SKILL.md and its runnable scripts, lives at github.com/brightdata/skills. New skills are added regularly, so star the repository to follow along.

How do I connect the Bright Data MCP server?

The Bright Data MCP server gives your agent live web access through 60+ tools for search, scraping, structured extraction and browser automation. It runs on the Web Unlocker API, so every request handles proxy rotation, anti-bot challenges and CAPTCHA solving. Each snippet below puts an API key in an agent config file. Those files are commonly committed to version control, so treat the key as you would any other secret. To avoid a long-lived key in a file entirely, the server also accepts OAuth 2.1, where the user signs in through a browser.
Then try it with a prompt like Extract the Bright Data overview section from LinkedIn.
Control token usage. Load only the tools you need with tool groups, for example groups=ecommerce,social, or name individual tools such as tools=web_data_amazon_product. A smaller tool list means a smaller context and more usable requests.
Two versions exist. The remote server is fully managed and needs no setup. The local server is self-hosted for on-premise or private cloud. See the MCP server overview for both, and the integration guides for other clients.

Should I use skills, MCP or both?

Skills and the CLI are the default pair. Skills carry the knowledge: which Bright Data product fits a task, how to authenticate, how to handle pagination and errors. The CLI executes. Neither costs a live request until the agent runs a command. The MCP server matters when an agent has no terminal. It exposes the same capabilities as tools inside the agent’s own loop, which is the only route for a hosted assistant or a client that cannot shell out. This page lists terminal access as a prerequisite, so MCP is optional here. Add it when you want live web access inside the tool loop rather than through a shell.

Frequently asked questions

No. npx skills add brightdata/skills and npx -y @brightdata/mcp both fetch on demand, so there is no global dependency to maintain. The Bright Data CLI can also run through npx: npx -p @brightdata/cli brightdata --version.
Yes. The MCP server draws from the same account-level free tier of 5,000 credits per month, from a single shared pool, because it runs on the Web Unlocker API. On team accounts that pool is shared across all users in the account.
No. Both the remote and local MCP servers authenticate with your API key only. Usernames in the format brd-customer-{customer_id}-zone-{zone_name} are for native proxy access, not MCP. If a third-party tool asks for a username, leave it empty.
Skills work across the 40+ agents in the open agent skills ecosystem, including Claude Code, Cursor and Codex. The MCP server works with any MCP-compatible client. llms.txt works with anything that can fetch a URL.
Yes. Give it a target URL and a sentence describing the fields you want, and the Bright Data CLI generates the scraper through Scraper Studio. Copy-pasteable prompts for the full build, run and self-heal loop are in Scraper Studio coding agent prompts.

Next steps

Choose a product

Match your target site to the right Bright Data product, then go straight to its first request.

Build a scraper with prompts

Copy-pasteable Claude Code, Cursor and Codex prompts that build, run and self-heal a scraper.

Bright Data CLI

Scrape, search, manage zones and control a remote browser from the terminal.