F
licenseNot graded
qualityD
maintenanceEnables web and local business searches through the Brave Search API. Provides general web search with pagination and filtering, plus local business search with automatic fallback to web results.
-
mcp-brave-search
by w-jeon
Brave Search MCP サーバー
Brave Search API を統合し、Web 検索機能とローカル検索機能の両方を提供する MCP サーバー実装。
特徴
ウェブ検索: 一般的なクエリ、ニュース、記事、ページ区切りと鮮度コントロール付き
ローカル検索: 詳細な情報でビジネス、レストラン、サービスを検索
柔軟なフィルタリング: 結果の種類、安全レベル、コンテンツの鮮度を制御
スマートフォールバック: ローカル検索では、結果が見つからない場合は自動的にウェブにフォールバックします。
Related MCP server: Brave Search MCP Server
ツール
勇敢なウェブ検索
ページネーションとフィルタリングを使用してウェブ検索を実行する
入力:
query（文字列）: 検索用語count（数値、オプション）: 1ページあたりの結果数（最大20件）offset（数値、オプション）：ページ区切りのオフセット（最大9）
勇敢なローカル検索
地元のビジネスやサービスを検索する
入力:
query（文字列）：ローカル検索用語count(数値、オプション): 結果の数（最大20）
ローカル検索結果が見つからない場合は自動的にウェブ検索に戻ります
構成
APIキーの取得
Brave Search APIアカウントにサインアップする
プランを選択してください（無料プランは月間2,000クエリまでご利用いただけます）
開発者ダッシュボードからAPIキーを生成する
Claude Desktopでの使用
これをclaude_desktop_config.jsonに追加します:
ドッカー
{
"mcpServers": {
"brave-search": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"BRAVE_API_KEY",
"mcp/brave-search"
],
"env": {
"BRAVE_API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}NPX
{
"mcpServers": {
"brave-search": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-brave-search"
],
"env": {
"BRAVE_API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}建てる
Dockerビルド:
docker build -t mcp/brave-search:latest -f src/brave-search/Dockerfile .ライセンス
このMCPサーバーはMITライセンスに基づいてライセンスされています。つまり、MITライセンスの条件に従って、ソフトウェアを自由に使用、改変、配布することができます。詳細については、プロジェクトリポジトリのLICENSEファイルをご覧ください。
Available Tools
2 toolsbrave_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:
Business names and addresses
Ratings and review counts
Phone numbers and opening hours Use this when the query implies 'near me' or mentions specific locations. Automatically falls back to web search if no local results are found.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | Number of results (1-20, default 5) | |
| query | Yes | Local search query (e.g. 'pizza near Central Park') |
TDQS
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries full burden. It discloses automatic fallback to web search and lists returned information (names, ratings, hours). It lacks details on rate limits or authorization, but the key behavior is transparent.
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 a concise paragraph with bullet points. It front-loads the purpose, then gives usage context, return info, and a fallback note. No unnecessary words, well-organized.
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?
No output schema, but description explains return details (business names, addresses, ratings, etc.) and fallback behavior. It misses error handling or pagination, but for a local search tool with two simple params, it is sufficiently complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% (both params described), baseline 3. The description adds meaning by specifying query examples ('pizza near Central Park') and default count behavior, plus clarifies what the return values include. This goes beyond schema.
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 searches for local businesses and places using Brave's Local Search API. It distinguishes from siblings like brave_web_search by specifying physical locations and business entities, and notes a fallback to web search.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'Best for queries related to physical locations' and 'Use this when the query implies "near me" or mentions specific locations,' providing clear when-to-use guidance. It does not explicitly state when not to use, but the context is strong.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | Number of results (1-20, default 10) | |
| offset | No | Pagination offset (max 9, default 0) | |
| query | Yes | Search query (max 400 chars, 50 words) |
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Mentions pagination, content filtering, freshness controls, and maximum results (20). However, does not explicitly state it is a read-only operation or discuss rate limits/auth. Adequate but not comprehensive.
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?
Three concise sentences: first states purpose, second provides usage scenarios, third mentions capabilities. No fluff, well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has 3 params and no output schema. Description covers purpose, usage, and constraints but lacks explanation of return value format or structure. Could be more complete for agent usage.
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 coverage is 100%; baseline 3. Description adds slight value by reiterating max 20 results and offset usage, but no new parameter details beyond schema. Content filtering and freshness controls are mentioned but are not parameters.
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?
Clearly states 'Performs a web search using the Brave Search API' with specific verb+resource. Distinguishes from siblings like brave_answers and brave_local_search by stating 'ideal for general queries, news, articles, and online content.'
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit usage context: 'ideal for general queries, news, articles, and online content. Use this for broad information gathering, recent events, or when you need diverse web sources.' Lacks explicit when-not-to-use or alternatives, but context is clear.
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.
2 tool updates
v1.0.0- First observed
brave_local_search - First observed
brave_web_search
TDQS
A4.2/5.0
Scored across 2 tools
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count3/5
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.
Completeness3/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues
Related MCP Connectors
Visit https://brave.com/search/api/ for a free API key. Search the web, local businesses, images,…
Brave Search MCP — independent web index (no Google/Bing dependency)
Search the web in real time to get trustworthy, source-backed answers. Find the latest news and co…
The best web search for your AI Agent
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceIntegrates Brave Search API to enable web, image, video, news, and local business searches with filtering options like result count and content freshness.270 npm-
- AlicenseNot gradedqualityDmaintenanceIntegrates the Brave Search API to provide web and local search capabilities, including news, articles, and business information. It features smart fallbacks from local to web search and supports pagination and freshness controls.270 npm1GPL 3.0
- AlicenseNot gradedqualityDmaintenanceIntegrates the Brave Search API to provide comprehensive web and local search capabilities. It enables users to perform general web queries, search for news, and find local business information with smart fallback functionality.23,542 npmMIT