How does this compare to using the Brave Search API directly?
This server wraps the API into an MCP/SSE interface, enabling seamless integration with AI models and clients that support the Model Context Protocol.
@Shoofio
基本情報
Stream Brave Search (web & local) results via a Model Context Protocol (MCP) / Server-Sent Events (SSE) interface. Acts as a centralized, observable tool provider for AI models, deployable via Docker or Helm.
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"brave-search-mcp-sse": {
"command": "docker",
"args": [
"pull",
"shoofio/brave-search-mcp-sse:latest"
]
}
}
}Performs a general web search using the Brave Search API.
Streams MCP messages containing search results (title, URL, snippet, etc.).
Performs a search for local businesses and places using the Brave Search API. Falls back to web search if no local results are found.
Streams MCP messages containing local business details (name, address, phone, rating, etc.).
An implementation of the Model Context Protocol (MCP) using Server-Sent Events (SSE) that integrates the Brave Search API, providing AI models and other clients with web and local search capabilities through a streaming interface.
Pull the Docker image from Docker Hub (shoofio/brave-search-mcp-sse) or deploy via Helm chart from https://shoofio.github.io/brave-search-mcp-sse/. Alternatively, run locally after cloning, building, and configuring the BRAVE_API_KEY environment variable. Clients connect via HTTP GET to the SSE endpoint (e.g., http://localhost:8080/sse).
This server wraps the API into an MCP/SSE interface, enabling seamless integration with AI models and clients that support the Model Context Protocol.
Node.js v22+ (for local development), Docker (for container deployment), or kubectl/Helm (for Kubernetes). A valid Brave Search API key is always required.
All search results are fetched live from the Brave Search API. The server does not store any search data locally.
It uses Server‑Sent Events (SSE) over HTTP, adhering to the Model Context Protocol (MCP). Clients connect to the `/sse` endpoint.
Web search supports `count` (1–20, default 10) and `offset` (0–9). Local search supports `count` (1–20, default 5). Rate limiting is logged but not enforced by the server.
Thordata MCP Server gives AI agents real-time access to Google, Bing, DuckDuckGo, and Yandex search through one MCP connection. It supports structured results, geo-targeting, language and device parameters, SEO monitorin
Hosted 3GPP MCP server: cited search across Rel-15 through Rel-20 TS/TR specs, recent TDocs, company proposals and meeting decisions. OAuth 2.1; no local index required.

Sourced privacy answers for AI assistants: how private an app or service is, private replacements for mainstream apps, privacy tool facts with sources, guides, MCP server vetting and free domain checks. Read-only, no acc

Search 4,000+ live UX, product-design and UX-research jobs from jobs.uxjobs.io — aggregated from 60+ applicant-tracking systems, re-verified against each employer, refreshed several times a day. Read-only, free, no sign-

Google Gemini MCP - Use Google's visual, video and chat capabilities in your AI Assistant. Uses MCP Apps to preview created images, landing pages, SVGs and video
コメント