Specific implementation researched
Brave Search API
Implementation, permissions and documented client compatibility.
A directory listing or verification does not replace a security audit. No installation is triggered automatically here. Do not enter API keys in public forms.
What is specifically documented?
- Connected service
- Brave Search API
- Publisher
- Brave
- Origin
- Officially from the named publisher
- Deployment mode
- Local
- Transport
- stdio standardmäßig; HTTP optional.
- Authentication
- BRAVE_API_KEY or BRAVE_API_KEY_FILE for the Brave Search API.
- Read capabilities
- Web, news, image and video search · Place and local search · LLM context and summaries
- Write capabilities
- No confirmed information
- Permissions
- Tool selection through allow/deny lists; the HTTP listener defaults to loopback only and has no authentication of its own.
- Required plan
- Brave Search API access; according to the repository, full local search and certain extras require a Pro plan.
- Additional costs
- No confirmed information
- Maintenance status
- No confirmed information
- Review date
- 11/10/2026
Support by client
Documented setup is not an independent functional test. General MCP support does not imply full compatibility.
| Client | Status | Source |
|---|---|---|
| Claude Desktop | Setup documented | Documentation ↗ |
| Claude Code | Not verified | — |
| Claude Web | Not verified | — |
| Cursor | Not verified | — |
Sources & implementation
GitHub - brave/brave-search-mcp-server · GitHub ↗Retrieved on 11/10/2026. Provider statements, not a security audit.
Implementation: https://github.com/brave/brave-search-mcp-server