mcp-brave-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRAVE_API_KEY | Yes | Your Brave Search API key. Get it at https://brave.com/search/api/ |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| brave_web_searchA | Search the web using Brave Search API. Returns relevant web pages with titles, URLs, and descriptions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusion or overlap. The tool's purpose is clearly defined and distinct.
The tool name 'brave_web_search' follows a descriptive verb_noun pattern, which is consistent and clear even as a standalone tool.
One tool is minimal for a server, but it is reasonable for a dedicated search API. Still, the server feels thin and could potentially benefit from additional search-related tools.
For a server focused solely on web search, the single tool covers the core functionality completely. There are no obvious gaps for basic web search use cases.