Log inSubmit server
MCP Omnisearch logo

MCP Omnisearch

Unifies web, AI, GitHub, and webpage extraction providers behind four MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Omnisearch

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-omnisearch": {
      "command": "npx",
      "args": [
        "-y",
        "mcpick"
      ],
      "env": {
        "TAVILY_API_KEY": "YOUR_VALUE_HERE",
        "KAGI_API_KEY": "YOUR_VALUE_HERE",
        "BRAVE_API_KEY": "YOUR_VALUE_HERE",
        "GITHUB_API_KEY": "YOUR_VALUE_HERE",
        "EXA_API_KEY": "YOUR_VALUE_HERE",
        "LINKUP_API_KEY": "YOUR_VALUE_HERE",
        "FIRECRAWL_API_KEY": "YOUR_VALUE_HERE",
        "FIRECRAWL_BASE_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y mcpick

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 10d ago.

Overview

The mcp-omnisearch MCP server gives agents one interface for web search, sourced AI answers, GitHub search, and web content extraction. It routes requests to configured providers including Tavily, Brave, Kagi, Exa, GitHub, Linkup, and Firecrawl, while skipping providers whose credentials are absent. Install it through MCPick or build and run it from source. Reach for it when an agent needs provider choice across search, research, code discovery, or webpage analysis.

Use cases

  • Search the web across multiple providers
  • Generate sourced answers for research questions
  • Find GitHub code, repositories, or users
  • Extract and summarize webpage content
  • Compare provider results for a single task

Key features

  • Unified web search across five provider options
  • Sourced AI answers with asynchronous research support
  • GitHub code, repository, and user search
  • Web extraction, crawling, scraping, and summarization
  • Optional provider credentials with partial operation
  • Inline or file-based handling for large results

Tools4

What MCP Omnisearch lets your agent do. Expand a tool for its parameters.

Self-reported~65 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 51d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 16d ago via OSV.dev · mcpick (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars359Stargazers on the source repository.
npm downloads518Package downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed4Callable tools this server registers over MCP.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Omnisearch works

What mcp-omnisearch does

The mcp-omnisearch MCP server consolidates several search and extraction services into four MCP tools. It connects to Tavily, Brave Search, Kagi, Exa AI, GitHub, Linkup, and Firecrawl, depending on the operation and provider selected. This arrangement lets an MCP client expose multiple backends without configuring one separate server per service.

The server supports four main workflows:

  • web_search searches the web through Tavily, Brave, Kagi, Exa, or Kagi Enrichment.
  • ai_search returns sourced answers from Kagi FastGPT, Exa Answer, Linkup, or Tavily Research.
  • github_search searches GitHub code, repositories, or users.
  • web_extract extracts, crawls, scrapes, summarizes, or finds similar content using Tavily, Kagi, Firecrawl, or Exa.

How it works

Each request selects a provider and supplies inputs appropriate to the chosen tool. Web searches can include controls such as result count, search depth, topic, date range, safe search, raw-content inclusion, and automatic parameters when the selected provider supports them. GitHub searches specify the search type and can use GitHub query syntax.

AI searches return sourced answers. Tavily Research may work asynchronously: the first call returns a task identifier, which must be supplied later as research_id to retrieve the report. Extraction requests can select a mode such as extract, provide a follow-up query, choose extraction depth, set chunks per source, and request Markdown output.

Providers without credentials are disabled rather than preventing the remaining configured providers from working. The mcp-omnisearch MCP server therefore supports partial provider setups, provided the selected operation has an available credentialed backend.

Setup and configuration

The published package can be added with MCPick using npx mcpick add, with mcp-omnisearch as the server name and npx -y mcp-omnisearch as the command and argument sequence. MCPick defaults to Claude Code; its --client and --scope options can target another client or a project-level configuration.

For a source installation, install dependencies with pnpm, build the project, and run node ./dist/index.js. Provider credentials are supplied through environment variables. Available variables cover Tavily, Kagi, Brave, GitHub, Exa, Linkup, and Firecrawl. FIRECRAWL_BASE_URL can point to a self-hosted Firecrawl instance.

Clients that support environment-variable expansion can reference secrets in MCP configuration instead of placing their values directly in the file. Expansion syntax and secret handling depend on the client. OMNISEARCH_LARGE_RESULT_MODE controls large-result handling, with file as the default and inline as the alternative.

Tools and capabilities

web_search is suited to current web research and supports several search providers. ai_search is intended for questions where a cited or sourced response is preferred over a list of links. github_search covers repository, code, and user discovery. web_extract handles page-level operations, including crawling and content transformation.

The mcp-omnisearch MCP server is a fit for agents that need to switch providers by task, use GitHub search alongside web research, or process a page after locating it. Provider-specific controls apply only where supported, so request behavior can differ between backends.

Limitations and notes

The server does not supply provider access by itself; credentials and any provider-specific account limits remain necessary. Missing keys cause those providers to be skipped. Search options are not guaranteed to have identical effects across providers because the implementation applies controls only when the selected service supports them.

Large responses can be returned inline or through files, according to OMNISEARCH_LARGE_RESULT_MODE. Remote deployments may require additional consideration for file-based responses. Firecrawl self-hosting requires a custom base URL, while Tavily Research requires a follow-up request to obtain the completed report after receiving its task ID.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Omnisearch

mcp-omnisearch is an MCP server that connects AI clients to Tavily, Brave, Kagi, Exa AI, GitHub, Linkup, and Firecrawl. Its main tools are web_search, ai_search, github_search, and web_extract, covering web queries, sourced answers, GitHub discovery, and webpage extraction.

Install it with MCPick using `npx mcpick add --name mcp-omnisearch --command npx --args=-y,mcp-omnisearch`. MCPick targets Claude Code by default; use `--client` and `--scope` for other client or project configurations.

It supports `TAVILY_API_KEY`, `KAGI_API_KEY`, `BRAVE_API_KEY`, `GITHUB_API_KEY`, `EXA_API_KEY`, `LINKUP_API_KEY`, and `FIRECRAWL_API_KEY`. Providers without keys are skipped, so only the services you use need credentials.

Yes, configure `FIRECRAWL_BASE_URL` for a self-hosted Firecrawl deployment. The server also accepts `FIRECRAWL_API_KEY` for Firecrawl authentication.

Set `OMNISEARCH_LARGE_RESULT_MODE` to `file` or `inline`; `file` is the default. File-based responses may require additional handling in remote deployments.

Related MCP servers

All in Search & Data Extraction All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Omnisearch AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-omnisearch?style=directory)](https://allmcps.com/mcp/mcp-omnisearch)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-omnisearch"><img src="https://allmcps.com/api/badge/mcp-omnisearch?style=directory" alt="MCP Omnisearch on AllMCPs" /></a>