Search

mcp-omnisearch

Multi-provider search aggregator. Unifies Tavily, Brave, Kagi, Exa, Perplexity, Linkup, Firecrawl, and GitHub behind a single interface.

Untested
View on GitHubby spences10

Install config

Claude Desktop (macOS)
// Requires provider API keys
{"mcpServers": {"omnisearch": {"command": "npx", "args": ["-y", "mcp-omnisearch@latest"], "env": {"TAVILY_API_KEY": "your-key", "BRAVE_API_KEY": "your-key"}}}}
Cursor
{"mcpServers": {"omnisearch": {"command": "npx", "args": ["-y", "mcp-omnisearch@latest"], "env": {"TAVILY_API_KEY": "your-key", "BRAVE_API_KEY": "your-key"}}}}
VS Code
// .vscode/mcp.json
{
  "servers": {
    "omnisearch": {
      "command": "npx",
      "args": ["-y", "mcp-omnisearch@latest"],
      "env": {"TAVILY_API_KEY": "your-key", "BRAVE_API_KEY": "your-key"}
    }
  }
}

Pros

  • +13 search providers in one server
  • +Auto-routing to best provider
  • +Docker deployment available

Cons

  • Requires multiple API keys for full functionality
  • Complex configuration
  • Some providers still require paid tiers

Best for

Multi-provider search, redundancy, research pipelines

Related servers in Search

Frequently asked questions

How do I install mcp-omnisearch?

Copy the config above into your AI assistant's MCP settings file:

  • Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Cursor: Settings → MCP → Add Server
  • VS Code: .vscode/mcp.json
Does it require an API key?

Yes. This server requires some form of configuration or credentials. Check the GitHub repository for setup instructions.

How were these results measured?

We run each server through a standardized test harness that:

  1. Installs the server via npx in a fresh environment
  2. Discovers available tools using the MCP SDK
  3. Executes real tasks (navigate, click, screenshot, etc.)
  4. Validates outputs with semantic assertions (not string matching)
  5. Measures latency percentiles and pass rate

All test scripts are open source on GitHub.

Related categories