MCP ConfigsMay 14, 2026·2 min read

mcp-omnisearch — Unified Search MCP Server

Run mcp-omnisearch as an MCP server to unify Tavily, Brave, Kagi, Exa, GitHub search, and extraction tools behind one interface.

Agent ready

This asset can be read and installed directly by agents

TokRepo exposes a universal CLI command, install contract, metadata JSON, adapter-aware plan, and raw content links so agents can judge fit, risk, and next actions.

Native · 94/100Policy: allow
Agent surface
Any MCP/CLI agent
Kind
Mcp
Install
Node|Pnpm
Trust
Trust: Established
Entrypoint
pnpm install && pnpm run build
Universal CLI install command
npx tokrepo install 5a328f21-6027-5e3e-b446-df5e659d9a41
Intro

Use mcp-omnisearch to give your agent a single MCP server for multi-provider web search and extraction workflows.

Run mcp-omnisearch as an MCP server to unify Tavily, Brave, Kagi, Exa, GitHub search, and extraction tools behind one interface.

Best for: agent builders who want one MCP endpoint that can fan out to multiple search/extraction providers with env-based keys

Works with: Node.js, pnpm, MCP clients that can run node dist/index.js, provider API keys via env vars

Setup time: ~10–20 minutes (install + build + client config)

Key facts (verified)

  • GitHub: 305 stars · 47 forks · pushed 2026-05-13.
  • License: MIT · owner avatar + repo URL verified via GitHub API.
  • Entrypoint (README-backed): pnpm install && pnpm run build.

Main

  • Start with one provider key enabled, then add more to avoid debugging multiple failures at once.
  • Keep provider keys scoped and rotate them; treat search/extraction as an external dependency with quotas and costs.
  • Add a thin policy layer in your agent: which providers are allowed for which task types and domains.

README excerpt (source)

# mcp-omnisearch

[![built with vite+](https://img.shields.io/badge/built%20with-Vite+-646CFF?logo=vite&logoColor=white)](https://viteplus.dev)
[![tested with vitest](https://img.shields.io/badge/tested%20with-Vitest-6E9F18?logo=vitest&logoColor=white)](https://vitest.dev)

A Model Context Protocol (MCP) server that provides unified access to
multiple search providers and AI tools. This server combines the
capabilities of Tavily, Brave, Kagi, Exa AI, GitHub, Linkup, and
Firecrawl to offer comprehensive search, AI responses, and content
processing through four consolidated tools.

<a href="https://glama.ai/mcp/servers/gz5wgmptd8">
  <img width="380" height="200" src="https://glama.ai/mcp/servers/gz5wgmptd8/badge" alt="Glama badge" />
</a>

## Features

### 🔍 `web_search` — Web Search

Search the web for information. Providers: tavily (factual/citations),
brave (privacy/operators), kagi (quality/operators), exa
(AI-semantic), kagi_enrichment (specialized indexes).

Parameters:

- `query` (string, required): Search query
- `provider` (string, required): `tavily`, `brave`, `kagi`, `exa`, or
  `kagi_enrichment`
- `limit` (number, optional): Maximum number of results (default: 10)

FAQ

Q: Do I need all providers configured? A: No—enable only the providers you have keys for; the config is env-driven.

Q: Where does it run? A: Your MCP client runs the Node entrypoint pointing at dist/index.js after build.

Q: How do I keep results consistent? A: Prefer a primary provider per task type and log which provider served each answer.

🙏

Source & Thanks

Source: https://github.com/spences10/mcp-omnisearch > License: MIT > GitHub: 305 stars · 47 forks · pushed 2026-05-13

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets