brave_web_searchLABSCO SUMMARY
Centralise the key, not the client.
The whole point of the SSE build is one API key on one server with many clients pointed at it, instead of a copy of the key in every developer's config. The Helm chart accepts an existing Kubernetes secret, so the key never has to appear in a values file you might commit.
What it is
A Brave Search server that speaks MCP over Server-Sent Events, built so an organisation can hold a single Brave API key centrally and give many clients controlled access to it.
What you get
brave_web_search— general web search withcount(1-20, default 10) andoffset(0-9, default 0)brave_local_search— businesses and places with address, phone number and ratings,count1-20 with a default of 5- A fallback that matters: a local query with no local results becomes a filtered web search instead of returning nothing
- Results streamed as MCP messages over SSE rather than delivered in one block
- Logging of requests, API interactions, errors and rate limits, so you can see who is spending the quota
Requirements
A Brave Search API key in BRAVE_API_KEY; a free tier is available. PORT defaults to 8080 and LOG_LEVEL is optional. Run shoofio/brave-search-mcp-sse:latest under Docker, or install the Helm chart for Kubernetes. Clients set transport to sse and point at a URL ending in /sse.
Setup effort
Run a container — pull the image, run it, then point your client at its URL
USE CASES
01
Giving a team web search without handing out the key
Run one server with the key, and let each client connect to its SSE endpoint.
02
Finding a business with details, not just links
Ask locally and get back address, phone number and rating — and a web search automatically when there is no local match.
03
Working out where the quota went
Read the request and rate-limit logs rather than guessing which client is spending the plan.
04
Paging through more than the first ten results
Raise count up to 20 and step the offset to reach later pages.
2 tools
Listed in project docs. Your client may show a different list.
brave_local_searchBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- Docker
- A Brave Search API key in BRAVE_API_KEY
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Pull the image, run it, then point your client at its URL.
Server setup
TERMINAL
docker pull shoofio/brave-search-mcp-sse:latest
docker run -d --rm -p 8080:8080 -e BRAVE_API_KEY="<YOUR_BRAVE_API_KEY>" --name brave-search-server shoofio/brave-search-mcp-sse:latestMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"brave-search": {
"url": "http://localhost:8080/sse"
}
}
}Start the container first; the server then listens at http://localhost:8080/sse. The URL path must end with /sse.
