# How to connect Brave Search to Claude

> Connect Brave Search to Claude through Agent200's MCP server: no separate key, ready-made tools and one API key.

- Page: https://www.agent200.com/tools/brave-search/framework/claude/
- Connector: [Brave Search](https://www.agent200.com/tools/brave-search.md)
- Framework: Claude
- Updated: 2026-11-15

## Instructions for AI agents

Goal: connect Brave Search to Claude with Agent200, through its MCP server.
Guide: https://www.agent200.com/tools/brave-search/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 Brave Search 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: "What are people saying about the new iPhone this week"
   What should come back:
   - An answer built from Brave Search results.
   - Behind the scenes, Claude calls an Agent200 tool for Brave Search, such as `brave_search_query_web`.
5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.

## Overview

This guide connects Brave Search to Claude through Agent200's MCP server. When you finish, Claude can search, read and act in Brave Search with the tools Agent200 provides, whenever a request needs them.

You add one MCP server to Claude with your Agent200 API key. Brave Search is reached with that key, so there is no separate Brave Search key to manage.

- **Connector:** [Brave Search](https://www.agent200.com/tools/brave-search/)
- **Works with:** Claude · Agent app, through MCP
- **Authentication:** Your Agent200 API key
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [5 tools](https://www.agent200.com/tools/brave-search/framework/claude/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **Brave Search 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 Brave Search to Claude

### 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 Brave Search and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

### 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.

### 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**.

### Step 4: Send your key as a request header

Under Authentication choose **No sign-in**. Open **Request headers**, pick `authorization`, enter `Bearer` followed by a space and your key, mark it Required and choose **Add**. Claude sends the value exactly as typed.

File `Add custom connector`:

```text
Remote MCP server URL:  https://api.agent200.com/mcp/
Authentication:         No sign-in
Request header name:    authorization
Value:                  Bearer YOUR_AGENT200_API_KEY
```

### 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

Ask: "What are people saying about the new iPhone this week"

What should come back:

- An answer built from Brave Search results.
- Behind the scenes, Claude calls an Agent200 tool for Brave Search, such as `brave_search_query_web`.

If Claude says it has no Brave Search tool, check that Brave Search is enabled for your project in the dashboard.

## Brave Search tools Claude can call

- **Search the web** (`brave_search_query_web`, read): Get ranked web results with titles, snippets and URLs.
- **Search news** (`brave_search_query_news`, read): Find recent news articles, filtered by freshness.
- **Search images** (`brave_search_query_images`, read): Find images that match a query.
- **Search videos** (`brave_search_query_videos`, read): Find videos that match a query.
- **Suggest queries** (`brave_search_get_suggestions`, read): Get autocomplete suggestions for a partial query.

## How it works

1. **You ask Claude.** In your own words, for something in Brave Search.
2. **Claude picks a tool.** It sees the Brave Search tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** It reaches Brave Search with your Agent200 API key, within the endpoints your project allows.
4. **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 Brave Search tools

Open + > Connectors in that chat and check Agent200 is on, and that no tool is set to Blocked under Customize > Connectors. Naming Brave Search in the request also helps.

### A tool call is refused or returns less than expected

Agent200 runs only what your project allows. Check that Brave Search 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](https://agent200.com/platform/apikeys/), 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.

## Use Brave Search with another framework

- [Brave Search + ChatGPT](https://www.agent200.com/tools/brave-search/framework/chatgpt.md)
- [Brave Search + Claude Code](https://www.agent200.com/tools/brave-search/framework/claude-code.md)
- [Brave Search + Muse](https://www.agent200.com/tools/brave-search/framework/muse.md)
- [Brave Search + Grok Bot](https://www.agent200.com/tools/brave-search/framework/grok-bot.md)
- [Brave Search + OpenAI Dots](https://www.agent200.com/tools/brave-search/framework/openai-dots.md)
- [Brave Search + Claude Duet](https://www.agent200.com/tools/brave-search/framework/claude-duet.md)
- [Brave Search + Hermes Agent](https://www.agent200.com/tools/brave-search/framework/hermes-agent.md)
- [Brave Search + OpenClaw](https://www.agent200.com/tools/brave-search/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
