Search MCP
Provides web search capabilities through the Brave Search API, including web search with filtering options (safe search, country, freshness), local POI lookups, and rich result fetching.
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., "@Search MCP find recent articles about AI advancements in healthcare"
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.
Search 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
SEARCH_MCP_...in your environment
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/search-mcp
npm i
npm run buildRelated MCP server: Brave Search MCP
Setup: Claude Code (CLI)
Use this one-liner (replace with your real values):
claude mcp add URL-Context-MCP -s user -e SEARCH_MCP_API_KEY="sk-your-real-key" -- npx @taiyokimura/url-context-mcp@latestTo remove:
claude mcp remove Search MCPSetup: Cursor
Create .cursor/mcp.json in your client (do not commit it here):
{
"mcpServers": {
"url-context-mcp": {
"command": "npx",
"args": ["@taiyokimura/url-context-mcp@latest"],
"env": { "SEARCH_MCP_API_KEY": "sk-your-real-key" },
"autoStart": true
}
}
}Other Clients and Agents
Install via URI or CLI:
code --add-mcp '{"name":"url-context-mcp","command":"npx","args":["@taiyokimura/url-context-mcp@latest"],"env":{"SEARCH_MCP_API_KEY":"sk-your-real-key"}}'Follow the MCP install guide and reuse the standard config above.
Command: npx
Args: ["@taiyokimura/url-context-mcp@latest"]
Env: SEARCH_MCP_API_KEY=sk-your-real-key
Type: STDIO
Command: npx
Args: @taiyokimura/url-context-mcp@latest
Enabled: true
Example ~/.config/opencode/opencode.json:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"url-context-mcp": {
"type": "local",
"command": ["npx", "@taiyokimura/url-context-mcp@latest"],
"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.url-context-mcp]
command = "npx"
args = ["@taiyokimura/url-context-mcp@latest"]
# Optional:
# SEARCH_MCP_API_KEY = "sk-your-real-key"
# MCP_NAME = "url-context-mcp"Configuration (Env)
SEARCH_MCP_API_KEY: Your API key (if applicable)
MCP_NAME: Server name override (default: url-context-mcp)
Available Tools
web_search
inputs: object { query: string (required), count?: number, offset?: number, safeSearch?: 'off'|'moderate'|'strict', country?: string, freshness?: 'pd'|'pw'|'pm'|'py', enableRichCallback?: boolean }
outputs: object (Brave Web Search API JSON)
local_pois
inputs: object { ids: string[] (1-20) }
outputs: object (Local POI API JSON)
local_descriptions
inputs: object { ids: string[] (1-20) }
outputs: object (Local descriptions API JSON)
rich_fetch
inputs: object { callback_key: string }
outputs: object (Rich results JSON)
Example invocation (MCP tool call)
{
"tool": "web_search",
"inputs": {
"query": "weather in munich",
"enableRichCallback": true
}
}Troubleshooting
401 auth errors: check SEARCH_MCP_API_KEY
Ensure Node 18+
Local runs: npx search-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
Specification: https://modelcontextprotocol.io/specification/2025-06-18/server/index
Brave Search API: https://api.search.brave.com/app/documentation
Name Consistency & Troubleshooting
Always use CANONICAL_ID (url-context-mcp) for identifiers and keys.
Use CANONICAL_DISPLAY (URL-Context MCP) only for UI labels.
Do not mix legacy keys after registration.
Consistency Matrix:
npm package name → @taiyokimura/url-context-mcp
Binary name → url-context-mcp
MCP server name (SDK metadata) → url-context-mcp
Env default MCP_NAME → url-context-mcp
Client registry key → url-context-mcp
UI label → URL-Context MCP
Conflict Cleanup:
Remove any stale keys (e.g., old display names) and re-add with url-context-mcp only.
Cursor: configure in the UI; this project intentionally omits .cursor/mcp.json.
Available Tools
4 toolslocal_descriptionsC
Fetch AI-generated descriptions for locations using Brave Local Search API
Inputs: ids (required).
local_poisC
Fetch extra information for locations using Brave Local Search API
Inputs: ids (required).
rich_fetchC
Fetch rich results using the callback_key from web_search
Inputs: callback_key (required).
web_searchC
Search the web using Brave Web Search API
Inputs: query (required), count, offset, safeSearch, +3 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 have some overlap in purpose, particularly between local_descriptions and local_pois, which both fetch location information using the same API and could be confused. However, web_search and rich_fetch are distinct in targeting general web search and rich results respectively, and the descriptions help clarify the differences.
The naming is mostly consistent with a clear pattern of using descriptive terms like 'local', 'web', and 'rich', all in snake_case. The only minor deviation is that rich_fetch uses 'fetch' while others use more specific verbs like 'search' or 'descriptions', but overall the pattern is readable and predictable.
With 4 tools, this server is well-scoped for a search-focused purpose, covering local descriptions, local points of interest, rich results, and general web search. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool surface covers key search operations for both web and local domains, with minor gaps such as no explicit tool for image or news search, but agents can likely work around this using the provided tools. The inclusion of rich_fetch as a callback from web_search adds useful functionality.
Related MCP Connectors
Web search API and MCP server for developers building AI agents.
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)
Serper MCP — wraps the Serper Google Search API (serper.dev)
Related MCP Servers
- -licenseNot gradedqualityBmaintenanceAn MCP server implementation that integrates the Brave Search API, providing both web and local search capabilities.27,402 npm91,952MIT
- 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 capabilities5991 npm131GPL 3.0

Brave Search MCP Serverofficial
AlicenseAqualityBmaintenanceAn MCP implementation that integrates the Brave Search API, providing comprehensive search capabilities including web, local business, image, video, news searches, and AI-powered summarization.849,999 npm1,579MIT- AlicenseAqualityDmaintenanceIntegrates Brave Search API to provide web, local, video, image, news, summarizer, place search, and LLM context capabilities through MCP.849,999 npmMIT