Earch MCP
Provides access to Brave's search APIs including web search, local points of interest (POIs), location descriptions, and rich search results with support for filtering by country, safe search settings, and content freshness
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., "@Earch MCP find nearby coffee shops open now"
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.
Earch MCP
The Universal MCP Server exposes tools for your workflows and is designed for prompt-first usage in MCP-compatible clients.
Installation
Prerequisites
Node.js 18+
Set
EARCH_MCP_API_KEYin your environment (orBRAVE_API_KEY)
Get an API key
If your tools require an external API, obtain a key from the provider’s docs/console.
Otherwise, you can skip this step.
Build locally
cd /path/to/earch-mcp
npm i
npm run buildRelated MCP server: Brave Search MCP Server
Setup: Claude Code (CLI)
Use this one-liner (replace with your real values):
claude mcp add Earch MCP -s user -e EARCH_MCP_API_KEY="sk-your-real-key" -- npx earch-mcpTo remove:
claude mcp remove Earch MCPSetup: Cursor
Create .cursor/mcp.json in your client (do not commit it here):
{
"mcpServers": {
"earch-mcp": {
"command": "npx",
"args": ["earch-mcp"],
"env": { "EARCH_MCP_API_KEY": "sk-your-real-key" },
"autoStart": true
}
}
}Other Clients and Agents
Install via URI or CLI:
code --add-mcp '{"name":"earch-mcp","command":"npx","args":["earch-mcp"],"env":{"EARCH_MCP_API_KEY":"sk-your-real-key"}}'Follow the MCP install guide and reuse the standard config above.
Command: npx
Args: ["earch-mcp"]
Env: EARCH_MCP_API_KEY=sk-your-real-key
Type: STDIO
Command: npx
Args: earch-mcp
Enabled: true
Example ~/.config/opencode/opencode.json:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"earch-mcp": {
"type": "local",
"command": ["npx", "earch-mcp"],
"enabled": true
}
}
}Add a new MCP and paste the standard JSON config.
See docs and reuse the standard config above.
Setup: Codex (TOML)
Example (Serena):
[mcp_servers.serena]
command = "uvx"
args = ["--from", "git+https://github.com/oraios/serena", "serena", "start-mcp-server", "--context", "codex"]This server (minimal):
[mcp_servers.earch-mcp]
command = "npx"
args = ["earch-mcp"]
# Optional environment variables:
# EARCH_MCP_API_KEY = "sk-your-real-key"
# MCP_NAME = "earch-mcp"Configuration (Env)
EARCH_MCP_API_KEY: Your API key (or BRAVE_API_KEY)
MCP_NAME: Server name override (default: earch-mcp)
Available Tools
web.search
inputs: { q: string, count?: number (<=50), country?: string, safesearch?: "off"|"moderate"|"strict", freshness?: "pd"|"pw"|"pm"|"py" }
outputs: JSON from Brave Web Search API
local.pois
inputs: { ids: string[1..20] }
outputs: JSON from Brave Local POIs API
local.descriptions
inputs: { ids: string[1..20] }
outputs: JSON from Brave Local Descriptions API
web.rich
inputs: { q: string }
outputs: JSON containing hint and rich callback result
Example invocation (MCP tool call)
{
"tool": "web.search",
"arguments": { "q": "brave search" }
}Troubleshooting
401 auth errors: check EARCH_MCP_API_KEY or BRAVE_API_KEY
Ensure Node 18+
Local runs: npx earch-mcp after npm run build
Inspect publish artifacts: npm pack --dry-run
References
Architecture: https://modelcontextprotocol.io/docs/learn/architecture
Server Concepts: https://modelcontextprotocol.io/docs/learn/server-concepts
Server Spec: https://modelcontextprotocol.io/specification/2025-06-18/server/index
Brave Search API: https://api.search.brave.com/res/v1/web/search
Brave Local API: https://api.search.brave.com/res/v1/local/pois
Brave Rich API: https://api.search.brave.com/res/v1/web/rich
Name Consistency & Troubleshooting
Always use CANONICAL_ID (earch-mcp) for identifiers and keys.
Use CANONICAL_DISPLAY (Earch MCP) only for UI labels.
Do not mix legacy keys after registration.
Consistency Matrix:
npm package name → earch-mcp
Binary name → earch-mcp
MCP server name (SDK metadata) → earch-mcp
Env default MCP_NAME → earch-mcp
Client registry key → earch-mcp
UI label → Earch MCP
Conflict Cleanup:
Remove any stale keys (e.g., old display names) and re-add with earch-mcp only.
Cursor: configure in the UI; this project intentionally omits .cursor/mcp.json.
Available Tools
4 toolslocal.descriptionsC
Brave Local Search AI descriptions: fetch descriptions for up to 20 location ids
Inputs: ids (required).
local.poisC
Brave Local Search POIs: fetch extra info for up to 20 location ids
Inputs: ids (required).
web.richC
Brave Rich Search via callback flow. First enables rich callback, then fetches rich data
Inputs: q (required).
web.searchC
Brave Web Search: returns results for query q
Inputs: q (required), count, country, safesearch, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
The tools are mostly distinct in purpose, with clear separation between local search (descriptions vs. POIs) and web search (rich vs. standard). However, the distinction between 'local.descriptions' and 'local.pois' could be slightly ambiguous without more context about what each returns, as both handle location IDs.
Naming is mostly consistent with a clear prefix pattern (local. vs. web.) and descriptive suffixes. Minor deviations exist, such as 'web.rich' being less conventional than 'web.search', but overall the naming is predictable and readable.
With 4 tools, the count is well-scoped for a search-focused server. Each tool appears to serve a specific function without redundancy, making the set manageable and appropriate for the domain of search operations.
The toolset covers basic search functionalities (local and web), but there are notable gaps. For example, there is no tool for updating or deleting search data, and advanced features like filtering or sorting are missing, which could limit agent workflows in a comprehensive search domain.
Maintenance
Related MCP Connectors
Visit https://brave.com/search/api/ for a free API key. Search the web, local businesses, images,…
Free web search, 130M+ business records, local search, weather and travel data for AI agents.
Web search, scraping, crawling, research, a browser agent, and company and people data.
Web data for agents. Extract web pages, crawl websites, discover URLs, and search the web.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables web searching and local business discovery through the Brave Search API. Provides both general web search with pagination and filtering controls, plus local business search with automatic fallback to web results.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.MIT
- 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.828 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.27,402 npmMIT