mcp-searxng and brave-search-mcp
These are competitor tools, as both implement an MCP server to provide web search capabilities, but integrate with different underlying search engines (SearXNG vs. Brave Search API).
About mcp-searxng
ihor-sokoliuk/mcp-searxng
MCP Server for SearXNG
Exposes two MCP tools: `searxng_web_search` with filtering by time range, language, and safe search level; and `web_url_read` for extracting markdown content with section filtering and paragraph range selection. Implements TTL-based caching for URL content and supports configurable proxy routing per tool, HTTP Basic Auth, and custom User-Agent headers for both search and content extraction interfaces.
About brave-search-mcp
mikechao/brave-search-mcp
An 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 capabilities
Exposes six distinct search tools through the Model Context Protocol, including a specialized `brave_llm_context_search` function that pre-extracts and tokenizes web content for RAG pipelines with configurable filtering modes. Supports both stdio and HTTP transport modes, with UI widgets for OpenAI Apps and MCP Apps that allow users to selectively control which results get added to model context. Built as an npm package requiring only a Brave Search API key to deploy, with fallback logic (e.g., local search defaults to web search if no location results found) for graceful degradation.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work