Brave Search MCP Server
by Anthropic (Model Context Protocol)
Expose the Brave Search API as MCP tools — web search, local search, and summarization for any MCP-compatible agent.
MCP
Brave Search MCP Server
Added 28 Jan 2025
Overview
Brave Search MCP Server wraps the Brave Search API as a set of Model Context Protocol tools, giving agents privacy-respecting access to web search, local business/place search, and AI-powered summarization without operating a custom crawler. It lives in the official `modelcontextprotocol/servers` monorepo (brave-search subdirectory) and is one of the most widely deployed reference MCP servers. Agents call the `brave_web_search` and `brave_local_search` tools to retrieve structured results they can reason over, cite, or pass to downstream tools. It works best with Claude Desktop and any MCP-compatible agent host, including Cursor, Windsurf, and custom agent runtimes that speak the MCP stdio transport.
Best for
Best for
Claude Desktop users and MCP-compatible agents that need privacy-respecting web and local search without managing a crawler
Use cases
- Give a Claude Desktop agent real-time web search without a custom backend
- Run local business or place lookups inside an agent workflow
- Bootstrap a research agent that needs general web context before reasoning
- Combine with a fetch/browser MCP for full search-then-read loops
Notes
What it does
Brave Search MCP Server translates the Brave Search API into MCP-native tools that any compatible agent can call directly. The two primary tools are brave_web_search (general web results with optional freshness and country filters) and brave_local_search (business and place results with addresses, ratings, and hours). An optional summarization surface lets agents request an AI-generated answer alongside raw results.
How to deploy
Install via npx or add it to your Claude Desktop claude_desktop_config.json under mcpServers. Set the BRAVE_API_KEY environment variable and the server is ready. No Docker, no persistent process — it runs as a child process spawned by the MCP host on demand.
Best practices
Pair with a fetch or browser MCP (Playwright, Puppeteer) for a full search-and-read loop: search first to find the right URLs, then fetch the full page content for deep reasoning. Cache repeated queries to stay within free-tier rate limits.
Pros
- Official reference implementation — kept current with MCP spec changes
- Exposes both web search and local/place search in a single server
- Privacy-respecting results with no Google API quota gymnastics
- Generous free tier; predictable paid pricing via Brave Search API
- Zero infrastructure — runs as a stdio process alongside any MCP host
Cons
- Requires a Brave Search API key (free tier available but rate-limited)
- Search quality on long-tail queries can lag behind Google
- Image and video result support is limited
- Summarization quality depends on Brave's AI layer, not the agent's model
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Brave Search MCP
Brave (reference implementation)
MCP server that gives any agent privacy-respecting web search via the Brave Search API. The default research primitive.
Playwright MCP
Microsoft
Browser control as an MCP server. Click, type, screenshot, scrape, all from inside any MCP-aware agent.
Puppeteer MCP Server
Model Context Protocol (reference)
Reference Puppeteer-backed MCP. Give an agent a real browser when an API does not exist.