Brave Search MCP Sse MCP Server

An MCP server implementation that integrates the Brave Search API, providing both web and local search capabilities. That is what the brave search mcp sse mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

An implementation of the Model Context Protocol (MCP) using Server-Sent Events (SSE) that integrates the Brave Search API, providing AI models and other clients with web and local search capabilities through a streaming interface.

This server acts as a tool provider for Large Language Models that understand the Model Context Protocol. It exposes Brave's powerful web and local search functionalities via an SSE connection, allowing for real-time streaming of search results and status updates.

• Web Search — Access Brave's independent web search index for general queries, news, articles, etc. Supports pagination and filtering controls
• Local Search — Find businesses, restaurants, and services with detailed information like address, phone number, and ratings
• Smart Fallbacks — Local search automatically falls back to a filtered web search if no specific local results are found for the query
• Server-Sent Events (SSE) — Efficient, real-time streaming of search results and tool execution status
• Model Context Protocol (MCP) — Adheres to the MCP standard for seamless integration with compatible clients
• Docker Support — Includes a Dockerfile for easy containerization and deployment

The tools it exposes

The server publishes 3 tools. What each one is for:

• Description — Performs a general web search using the Brave Search API
• Inputs — * query (string, required): The search query
• Output — Streams MCP messages containing search results (title, URL, snippet, etc.)

What it needs from you

Configuration is passed through the environment: BRAVE_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Depending on your chosen deployment method, you will need some of the following: * Brave Search API Key: Required for all deployment methods. See "Getting Started" below. * Docker: Required if deploying using Docker. * kubectl & Helm: Required if deploying to Kubernetes using Helm. * Node.js & npm: Required only for local development (Node.js v22.x or later recommended). *

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Among the search and retrieval options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Brave Search MCP Sse's toolset — Description, Inputs, Output — is a fair guide to whether it matches your workflow. It is maintained by Shoofio; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Brave Search MCP Sse's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.