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 https://api-dashboard.search.brave.com/app/keys |
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 targets physical locations and businesses with local context, while brave_web_search handles general web content and information. Their descriptions explicitly differentiate use cases ('near me' vs. 'general queries'), eliminating any overlap or confusion.
Both tools follow a consistent naming pattern: 'brave_' prefix followed by a descriptive term (local_search, web_search). This uniformity makes them easily recognizable as part of the same server and clearly indicates their function.
With only two tools, the server feels thin for a search domain that could benefit from more specialized operations (e.g., image search, news search, or advanced filtering). While the tools cover core local and web search, the limited count may restrict agent flexibility in handling diverse search-related tasks.
The server covers basic local and web search functionalities, but there are notable gaps for a comprehensive search toolset. Missing operations include image/video search, news-specific search, autocomplete suggestions, or trend analysis, which could limit agents in fully addressing search-related queries.