-
licenseNot graded
qualityA
maintenanceAn MCP server implementation that integrates the Brave Search API, providing both web and local search capabilities.
13,250
90,196
MIT
mcp-brave-search
Provides web search capabilities using the Brave Search API, returning relevant web pages with titles, URLs, and descriptions. Supports parameters for result count, pagination, safe search, freshness, language, and country.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-brave-searchSearch the web for the latest advancements in renewable energy from the past month"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Brave Search
Serveur MCP pour agents IA - recherche web via l'API Brave Search.
🔑 Prérequis
Clé API Brave Search (gratuit, 2000 requêtes/mois) : https://brave.com/search/api/
Related MCP server: MCP2Brave
⚙️ Configuration agent
{
"mcpServers": {
"brave-search": {
"command": "npx",
"args": ["-y", "github:Llamatron2112/mcp-brave-search"],
"env": {
"BRAVE_API_KEY": "votre_clé_api"
}
}
}
}đź“‹ Outil brave_web_search
Paramètre | Type | Requis | Défaut |
| string | ✅ | — |
| number | non | 10 (1-20) |
| number | non | 0 |
| string | non | moderate |
| string | non | all |
| string | non | "fr", "en"… |
| string | non | "FR", "US"… |
🏗️ Dev
npm install && npm run build
npm startLicense
MIT
Available Tools
1 toolbrave_web_searchA
Search the web using Brave Search API. Returns relevant web pages with titles, URLs, and descriptions.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | Number of results to return (default: 10, max: 20) | |
| query | Yes | The search query string | |
| offset | No | Number of results to skip for pagination (default: 0) | |
| country | No | Country code for localized results (e.g., 'FR', 'US', 'GB', 'DE') | |
| freshness | No | Filter results by time period | all |
| safesearch | No | Safe search filter level | moderate |
| search_lang | No | Language code for search results (e.g., 'fr', 'en', 'es', 'de') |
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the return format ('relevant web pages with titles, URLs, and descriptions'), which is helpful. However, with no annotations provided, the description carries the burden for behavioral disclosure, and it does not mention rate limits, error behavior, or other non-obvious traits. It partially fulfills the requirement.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences that front-load the verb and resource. There is zero wasted text, and every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (7 parameters, no output schema, no annotations), the description is sufficient. The schema handles parameter details, and the description covers purpose and return format. It could mention rate limits or pagination, but those are not critical for a simple search tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The main description adds no parameter-specific meaning beyond what the schema already provides, but it does not need to since all parameters are well-documented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function with a specific verb and resource: 'Search the web using Brave Search API.' It also specifies the output format ('Returns relevant web pages with titles, URLs, and descriptions'), leaving no ambiguity about the tool's purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit guidance on when to use this tool or alternatives, but with no sibling tools, the context is clear. The description implies usage for web search but does not provide explicit when-to-use or when-not-to-use instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
brave_web_search
TDQS
A4/5.0
Scored across 1 tool
Disambiguation5/5
With only a single tool, there is no possibility of confusion or overlap. The tool's purpose is clearly defined and distinct.
Naming Consistency5/5
The tool name 'brave_web_search' follows a descriptive verb_noun pattern, which is consistent and clear even as a standalone tool.
Tool Count3/5
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.
Completeness5/5
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.
Maintenance
ActivitySlowing
ResponsivenessNo issues
Related MCP Connectors
Serper MCP — wraps the Serper Google Search API (serper.dev)
MCP server for Google search results via SERP API
Docs: https://docs.keenable.ai/mcp-server Keenable is a free, remote MCP server that gives agents access to the web index. Search the web with ranked results and date/site filters, then fetch any indexed page as clean markdown. Works out of the box with no account or API key.
Related MCP Servers
- AlicenseCqualityDmaintenanceA server based on the MCP protocol that uses the Brave API for web search functionality.63MIT
- AlicenseNot gradedqualityFmaintenanceAn MCP server that integrates the Brave Search API to provide both web and local search capabilities, with features like pagination, filtering, and smart fallbacks.15MIT
- AlicenseAqualityDmaintenanceAn MCP Server implementation that integrates the Brave Search API, providing, Web Search, Local Points of Interest Search, Image Search, Video Search, News Search and LLM Context Search capabilities5102125GPL 3.0