MCP2Brave
Related Servers
Alternatives to MCP2Brave
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityAmaintenanceAn MCP server implementation that integrates the Brave Search API, providing both web and local search capabilities.23,542 npm91,120MIT
- AlicenseAqualityDmaintenanceAn MCP server for integrating with the Brave Search API, and it supports HTTP proxying.28 npm3JavaScriptMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that integrates the Brave Search API to provide both web and local search capabilities, with features like pagination, filtering, and smart fallbacks.15MIT
- AlicenseAqualityBmaintenanceMCP server for web search using the Brave Search API, supporting filters for freshness, language, country, and safe search.112 npmMIT
- AlicenseBqualityFmaintenanceAn MCP server that enables users to fetch Python documentation using the Brave Search API through natural language queries.1Apache 2.0
- 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 capabilities5399 npm127GPL 3.0
TDQS
Scored across 6 tools
Multiple tools have unclear boundaries and overlapping purposes. 'brave_search_summary' and 'search_brave_with_summary' appear to serve the same function with only minor wording differences. Similarly, 'get_url_content_direct' and 'url_content' are essentially duplicates with one in English and one in Chinese. This creates significant ambiguity for agent selection.
The naming conventions are inconsistent and chaotic. There's a mix of snake_case ('brave_search_summary') and lowercase with underscores ('search_brave_with_summary'), plus inconsistent verb usage ('get_' vs just the noun 'url_content'). The bilingual naming (English and Chinese) further compounds the inconsistency with no discernible pattern.
With 6 tools, the count is reasonable for a search/content retrieval server. However, since 4 of these tools are essentially duplicates (2 search pairs and 2 URL content pairs), the effective tool count is much lower, making the server feel thin despite the nominal count being appropriate.
The server covers basic search and content retrieval operations, but there are notable gaps. While it provides search (general and news) and URL fetching, there's no way to filter search results, handle pagination, or access more advanced Brave Search features. The duplication of tools doesn't add functional coverage, leaving the surface incomplete for robust web interaction.