Bright Data + Claude
How to connect Bright Data to Claude
Connect Bright Data to Claude through Agent200's MCP server: no separate key, ready-made tools and one API key.
On this page
Overview
This guide connects Bright Data to Claude through Agent200's MCP server. When you finish, Claude can search, read and act in Bright Data with the tools Agent200 provides, whenever a request needs them.
You add one MCP server to Claude with your Agent200 API key. Bright Data is reached with that key, so there is no separate Bright Data key to manage.
- Connector
- Bright Data
- Works with
- Claude ยท Agent app, through MCP
- Authentication
- Your Agent200 API key
- You need
- An Agent200 API key
- Tools
- 5 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Bright Data enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- Claude, with custom MCP servers allowed. Custom connectors are on every Claude plan (Free: one). Sending an API key uses the Request headers option, a beta that only some accounts have; on Team and Enterprise an Owner adds the connector for everyone.
Connect Bright Data to Claude
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude in the next step, as "Authorization: Bearer <your key>". One key covers Bright Data and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Open Connectors in Claude
On a Free, Pro, Max or Ultra plan, go to Customize > Connectors. On Team or Enterprise, an Owner goes to Organization settings > Connectors; members then find the connector under Customize > Connectors.
-
3
Step 3: Add a custom connector
Select Add, then Add custom connector. Enter a name, Agent200, and the remote MCP server URL, then choose Continue.
-
4
Step 4: Send your key as a request header
Under Authentication choose No sign-in. Open Request headers, pick
authorization, enterBearerfollowed by a space and your key, mark it Required and choose Add. Claude sends the value exactly as typed.Add custom connectorMCP: Claude custom connector (URL and request header) Remote MCP server URL: https://api.agent200.com/mcp/ Authentication: No sign-in Request header name: authorization Value: Bearer YOUR_AGENT200_API_KEY -
5
Step 5: Turn it on in a chat
In a chat, select + > Connectors and turn Agent200 on. Ask Claude to list the Agent200 tools to check the connection; Claude asks before a tool runs the first time.
Test your connection
Run one request to check everything is wired up.
Ask
Get the top Google results for best CRM for startups
What should come back
- A result from Bright Data, returned through your Agent200 API key.
-
Behind the scenes, Claude calls
bright_data_search_engine.
If a tool is refused, check that Bright Data is switched on for your project in the Agent200 dashboard.
Get your API key
Create a key in the Agent200 dashboard. It reaches Bright Data and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Bright Data to Claude.
Goal: connect Bright Data to Claude with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/bright-data/framework/claude/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Claude's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Bright Data is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Claude: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Claude's exact menus or commands. 4. Check it works with this request: "Get the top Google results for best CRM for startups" What should come back: - A result from Bright Data, returned through your Agent200 API key. - Behind the scenes, Claude calls `bright_data_search_engine`. 5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/bright-data/framework/claude.md
Bright Data tools Claude can call
-
Search the web
Readbright_data_search_engineGet search engine results for a query.
-
Fetch a page
Readbright_data_scrape_urlGet the content of a web page as HTML or Markdown.
-
Start a scraper
Writebright_data_trigger_scraperStart a collection job on a site scraper for a list of URLs.
-
Check a job
Readbright_data_get_snapshot_statusGet the progress of a collection job.
-
Download results
Readbright_data_get_snapshotDownload the structured results of a finished job.
No tool matches that search.
How it works
-
01
You ask Claude
In your own words, for something in Bright Data.
-
02
Claude picks a tool
It sees the Bright Data tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
It reaches Bright Data with your Agent200 API key, within the endpoints your project allows.
-
04
Claude answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Permissions at every level. Your project settings decide which services and endpoints the agent may use.
Troubleshooting
There is no Request headers section
Request headers are a Claude beta that only some accounts have. Without it, Claude cannot send an API key to a custom connector: use Claude Code, or the Agent200 SDK in your own agent.
Claude cannot reach the server
Check the header value is Bearer, a space, then your key, and that the URL is exactly the Agent200 MCP server address.
A Team or Enterprise member cannot add the connector
Only an Owner adds custom connectors, in Organization settings > Connectors. Members then connect it under Customize > Connectors.
You created a new API key
Claude does not let you edit a connector’s authentication. Remove the Agent200 connector and add it again with the new key.
Claude does not use the Bright Data tools
Open + > Connectors in that chat and check Agent200 is on, and that no tool is set to Blocked under Customize > Connectors. Naming Bright Data in the request also helps.
A tool call is refused or returns less than expected
Agent200 runs only what your project allows. Check that Bright Data and the tools you need are enabled in the dashboard's Connectors settings.
The API key was pasted into a chat or committed
Create a new key on the API keys page, replace it in Claude's MCP settings, and stop using the old one. Paste the key only into Claude's settings, never into a chat.
