Brave Search

MCP ServerPaid

Brave Search MCP connects an AI assistant to Brave Search for real-time web searches. Brave describes its API results as including structured web results, news, local search, and AI-optimized snippets.

Last updated: October 31, 2026

Official. Built and maintained by the company or project behind the service, so usually kept in step with it. Not audited by us.
Community. Built and maintained by an independent developer or group, not by the company behind the service. The company has not reviewed it, and updates depend on its author.

About Brave Search

Brave Search MCP connects an AI assistant to Brave Search through the Model Context Protocol. It gives the assistant access to real-time web searches, so it can retrieve information from the web as part of an interaction or research workflow. Brave describes its API results as including structured web results, news, local search, and AI-optimized snippets. The server is a way to make search available to an MCP-compatible workflow; it is not described in the reviewed materials as a tool for changing external services.

What can Brave Search do?

The verified materials describe access to Brave Search for real-time web searches. Brave says its API results can include structured web results, news, local search, and AI-optimized snippets. These result types can support workflows that need web information, current news, local search results, or content prepared for AI use.

The official pages reviewed do not enumerate the server’s complete tool names or argument schemas. Rather than promise a particular set of callable tools, the listing can describe the documented result groups:

Real-time web searches through Brave Search.
Structured web results from the Brave Search API.
News and local search results.
AI-optimized snippets.

How Brave Search connects and authenticates

Brave documents a local MCP-server configuration for Claude Desktop and also documents a container-image deployment path for local use or deployment on AWS AgentCore, Amazon ECS, and Amazon EKS. The documented setup authenticates with a Brave Search API key and requires a Brave API account. API use is metered under the selected plan. Claude Desktop is the client explicitly documented for this server; Brave’s broader tools page lists other clients and integrations, but does not establish that each works with this specific server. The reviewed sources do not specify a complete client compatibility matrix or transport options beyond the documented local configuration and container deployment.

Who is Brave Search best for?

This server suits people building or using an AI assistant workflow that needs Brave Search results during a conversation or research task. It is relevant to users who want access to web, news, or local search through MCP, including teams considering the documented container deployment options. Users need a Brave Search API account and API key, and should select a Brave API plan for their intended use. The documented API plans are metered; their prices are API charges, not a separately stated MCP-server fee.

What Brave Search can access and change

With its API key, the documented server accesses Brave Search through the API for search-related results. Brave describes structured web results, news, local search, and AI-optimized snippets. The reviewed official materials do not describe the server as able to write to or modify user data or external services, and they do not document consequential or irreversible actions. The specific tools, argument schemas, and complete client compatibility are not enumerated in the materials reviewed, so those details should not be assumed from this description.

Alternatives to Brave Search

For another search-focused MCP option, consider DuckDuckGo MCP Server, which is also named as a search server in this directory. Exa Official MCP Server and Tavily Official MCP Server are other directory entries with search-oriented names. Compare their own listing details to determine their documented capabilities and requirements; this comparison does not imply feature parity.

Visit Website

Key Features

Connects an AI assistant to Brave Search for real-time web searches through MCP.

Brave describes API results as including structured web results, news, local search, and AI-optimized snippets.

A Brave Search API account and API key are required; API use is metered under the selected plan.

Brave documents a local MCP-server setup for Claude Desktop.

Brave documents container-image deployment locally or on AWS AgentCore, Amazon ECS, and Amazon EKS.

The documented server performs search/API access; reviewed materials do not describe it as modifying user data or external services.

Before you installSecurity checklist for MCP servers

An MCP server runs code and gives your AI assistant access to files, accounts or data. A few minutes of checking is worth it.

Check the source. Make sure the repository belongs to the vendor or author you expect, that the vendor's own documentation links to it, and that it is actively maintained. Beware of lookalike names.
Read what it can do. Look at the tools the server exposes and the permissions or scopes it asks for. Start with read-only access where the server allows it.
Use the least access that works. Give it a dedicated API key or a narrowly scoped token, ideally on a test project or sandbox, not your production credentials.
Pin versions and review updates. Install a specific version, read changes before upgrading, and do not run copied commands you do not understand.
Treat what it returns as untrusted. Documents, web pages and tool results can contain text that tries to steer your AI assistant. Keep confirmation switched on for actions that write, delete, send or spend.
Know where your data goes. Find out whether the server runs on your machine or is hosted, and what it sends to the vendor or to third parties.
Keep a way back. Know how to revoke the key and remove the server from your client's configuration.

This page is general information, not security or legal advice, and listing a server is not an endorsement or a security review. We do not create, host or control MCP servers, and listing details such as commands, permissions or pricing can be out of date, so check the official source. You install and use MCP servers at your own risk. See the section on third-party products in our Terms of Service.

Pricing Plans

Search API

$5.00 per 1,000 requests

Provides Brave Search API access for MCP search requests.
The pricing page states that the plan includes $5 in free credits each month.
API use is metered; a Brave API account and API key are required.
Suits users connecting an assistant to Brave Search; the facts do not specify a separate MCP-server fee.

Answers API

$4.00 per 1,000 queries + $5.00 per 1,000,000 input tokens + $5.00 per 1,000,000 output tokens

Provides an Answers API plan; the verified facts do not detail its MCP tool behavior.
The pricing page states that the plan includes $5 in free credits each month.
Usage is priced by queries and input and output tokens.
Requires a Brave API account and API key; this is API pricing, not a separate MCP-server fee.

Pricing information last updated: October 31, 2026

Visit Website

FAQs

What does Brave Search MCP connect to?

It provides an MCP interface to Brave Search for real-time web searches. Brave describes API results as including structured web results, news, local search, and AI-optimized snippets.

What do I need to authenticate?

The documented setup requires a Brave Search API account and an API key. API use is metered under the selected Brave API plan.

Can I run the server locally?

Brave documents a local configuration for Claude Desktop. It also documents container-image deployment locally or on AWS AgentCore, Amazon ECS, and Amazon EKS.

Can the server change my data or other services?

The reviewed official materials describe search/API access and do not describe the server as writing to or modifying user data or external services.

Which clients are confirmed to work with this specific server?

Brave documents the server with Claude Desktop. Its tools page names other clients and integrations, but the verified facts do not establish that each is compatible with this specific server.