tavily-mcp and mcp-omnisearch
The first is a specialized search provider that the second wraps as one option among multiple search backends, making them complements designed to be used together within a unified search abstraction layer.
About tavily-mcp
tavily-ai/tavily-mcp
Production ready MCP server with real-time search, extract, map & crawl.
Provides four specialized web tools—search, extract, map, and crawl—integrated via the Model Context Protocol for seamless AI assistant connectivity. Supports both local deployment (Node.js-based) and remote hosting via Tavily's hosted MCP endpoint, with flexible authentication through API keys or OAuth. Integrates directly with Claude Desktop, Cursor, and Claude Code via HTTP transport with configurable default parameters.
About mcp-omnisearch
spences10/mcp-omnisearch
🔍 A Model Context Protocol (MCP) server providing unified access to multiple search engines (Tavily, Brave, Kagi), AI tools (Perplexity, FastGPT), and content processing services (Jina AI, Kagi). Combines search, AI responses, content processing, and enhancement features through a single interface.
# Technical Summary Implements four consolidated MCP tools (web_search, ai_search, github_search, web_extract) with pluggable provider backends, allowing clients to query multiple APIs through a unified interface while gracefully degrading based on available credentials. Supports advanced search operators native to Brave/Kagi, domain filtering via API parameters, and specialized extractors like Firecrawl's interactive scraping and Kagi's multimodal summarization (pages, videos, podcasts). Designed for integration with AI assistants (Claude Desktop, Cline) via environment-variable configuration with zero hard dependencies on any single provider.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work