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 obtained from the developer dashboard |
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_searchA | Performs a web search using the Brave Search API, ideal for general queries, news, articles, and online content. Use this for broad information gathering, recent events, or when you need diverse web sources. Supports pagination, content filtering, and freshness controls. Maximum 20 results per request, with offset for pagination. |
| brave_local_searchA | Searches for local businesses and places using Brave's Local Search API. Best for queries related to physical locations, businesses, restaurants, services, etc. Returns detailed information including:
|
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: brave_local_search is for local business and place queries (e.g., 'near me'), while brave_web_search is for general web searches (e.g., news, articles). Their descriptions explicitly differentiate use cases, making misselection unlikely.
Both tools follow a consistent verb_noun pattern with 'brave_' prefix and snake_case: brave_local_search and brave_web_search. This predictable naming scheme enhances readability and agent usability.
With only 2 tools, the server feels thin for a search domain, potentially limiting functionality. While it covers local and web search basics, more specialized tools (e.g., image search, news search) could enhance completeness. The count is borderline but reasonable for a minimal setup.
The server covers core search types (local and web), but there are notable gaps for a search API, such as image search, video search, or news-specific search. Agents can work around this by using web search broadly, but the surface is incomplete for comprehensive search operations.