Brave Search MCP Server
Related Servers
Alternatives to Brave Search MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceIntegrates the Brave Search API into AI assistants to enable web and local business search capabilities. This allows models to perform real-time information retrieval and locate places using the Model Context Protocol.1MIT
- 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.361 npm1GPL 3.0
- AlicenseAqualityCmaintenanceIntegrates Brave Search API to provide web, local, video, image, news, summarizer, place search, and LLM context capabilities through MCP.817,443 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to perform web searches using the Brave Search engine, providing an independent alternative to Google/Bing.2 npmMIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server that provides real-time web search capabilities to AI assistants through pluggable search providers, currently integrated with the Brave Search API.516MIT
- 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.361 npm-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one is for local business/place searches and the other is for general web searches. The descriptions explicitly differentiate their domains (local vs. web), making it impossible to confuse them. Each tool serves a unique function within the search domain.
Both tools follow a perfectly consistent naming pattern: 'brave_' prefix followed by descriptive snake_case (local_search, web_search). The naming convention is uniform across all tools, making them predictable and easy to understand. There are no deviations or mixed styles.
With only 2 tools, the server feels somewhat thin for a search domain that could benefit from more specialized operations (e.g., image search, news search, autocomplete). While the two core search functions are covered, the limited tool count may restrict agent capabilities for broader search-related tasks. It's borderline minimal but functional.
The server covers the essential search operations (local and web) well, but there are minor gaps in the search surface. For instance, no tools for image search, news search, or search suggestions/autocomplete are included, which are common in search APIs. However, the core workflows are adequately supported, and agents can work around these omissions.