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.
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.
- `brave_web_search` — general web search with `count` (1-20, default 10) and `offset` (0-9, default 0)
- `brave_local_search` — businesses and places with address, phone number and ratings, `count` 1-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
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`.
One command plus a key — docker pull shoofio/brave-search-mcp-sse:latest, then supply credentials