mcp-brave-search
README.md
# 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/
## ⚙️ Configuration agent
```json
{
"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 |
|-----------|------|--------|--------|
| `query` | string | ✅ | — |
| `count` | number | non | 10 (1-20) |
| `offset` | number | non | 0 |
| `safesearch` | string | non | moderate |
| `freshness` | string | non | all |
| `search_lang` | string | non | "fr", "en"… |
| `country` | string | non | "FR", "US"… |
## 🏗️ Dev
```bash
npm install && npm run build
npm start
```
## License
MITTDQS
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