Brave Search MCP 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 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| brave_web_searchC | Execute web search using Brave Search API with improved results |
| brave_local_searchC | Search for local businesses and places |
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 2 tools
The two tools have clearly distinct purposes: one is for local business/place searches and the other is for general web searches. The descriptions explicitly differentiate their domains (local vs. web), making it impossible to confuse them. Each tool serves a unique function within the search domain.
Both tools follow a perfectly consistent naming pattern: 'brave_' prefix followed by descriptive snake_case (local_search, web_search). The naming convention is uniform across all tools, making them predictable and easy to understand. There are no deviations or mixed styles.
With only 2 tools, the server feels somewhat thin for a search domain that could benefit from more specialized operations (e.g., image search, news search, autocomplete). While the two core search functions are covered, the limited tool count may restrict agent capabilities for broader search-related tasks. It's borderline minimal but functional.
The server covers the essential search operations (local and web) well, but there are minor gaps in the search surface. For instance, no tools for image search, news search, or search suggestions/autocomplete are included, which are common in search APIs. However, the core workflows are adequately supported, and agents can work around these omissions.