MCP Brave Search Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRAVE_API_KEY | Yes | Your Brave Search API key, required to use the Brave 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 |
|---|---|
| internet_searchA | Performs a web search using the Brave Search API. Returns relevant websites, snippets, and URLs. Optionally displays news results. |
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
Only one tool exists, so there is no possibility of confusing it with another. The tool's purpose is clear and distinct.
The single tool name 'internet_search' follows a clear verb_noun pattern, which is consistent and predictable even though there is only one tool.
The server has only one tool, which feels thin for a typical server, but given the narrow scope of performing web searches, it is borderline acceptable rather than excessive.
The domain is web search, and the single tool fully covers that domain by performing searches and returning results. There are no obvious missing operations for the stated purpose.