mcp-omnisearch MCP Server

A Model Context Protocol (MCP) server that provides unified access to Tavily, Brave, Kagi, Exa AI, GitHub, Linkup, and Firecrawl through four consolidated tools.

Local serverstdioMIT

What is the mcp-omnisearch MCP Server?

mcp-omnisearch source profile. From the maintainer documentation: “A Model Context Protocol (MCP) server that provides unified access to Tavily, Brave, Kagi, Exa AI, GitHub, Linkup, and Firecrawl through four consolidated tools.”

Installation

The documented npm package is mcp-omnisearch. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.

Configuration values

The example declares TAVILY_API_KEY, EXA_API_KEY. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.

Source

Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
web_search
ai_search
github_search
web_extract

How to install the mcp-omnisearch MCP Server

{
  "mcpServers": {
    "mcp-omnisearch": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-omnisearch"
      ],
      "env": {
        "TAVILY_API_KEY": "YOUR_TAVILY_API_KEY",
        "EXA_API_KEY": "YOUR_EXA_API_KEY"
      }
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Configuration

VariableDescriptionRequired
TAVILY_API_KEYDeclared in the maintainer’s client configuration.Check documentation
EXA_API_KEYDeclared in the maintainer’s client configuration.Check documentation