mcp-omnisearch MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

4 tools cover search, AI-search, GitHub, and extraction — no tool-sprawl
Bring-your-own-keys per provider; use only what you pay for
Tavily, Brave, Kagi, Exa for search; Kagi FastGPT, Exa, Linkup for AI search
Firecrawl self-hosted support via FIRECRAWL_BASE_URL
Docker + OpenAPI (MCPO) available for remote deployments

Live-Demo

In der Praxis

omnisearch.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "omnisearch": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-omnisearch"
      ],
      "_inferred": true
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "omnisearch": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-omnisearch"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "omnisearch": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-omnisearch"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "omnisearch": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-omnisearch"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "omnisearch",
      "command": "npx",
      "args": [
        "-y",
        "mcp-omnisearch"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "omnisearch": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "mcp-omnisearch"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add omnisearch -- npx -y mcp-omnisearch

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: mcp-omnisearch

Research a topic with fallback across multiple search engines

👤 Researchers, analysts, anyone who's been burned by a single engine's bias ⏱ ~15 min beginner

Wann einsetzen: A fresh topic where one engine's top-10 often differs from another's.

Voraussetzungen

At least one search API key (Tavily free tier is easiest) — tavily.com/signup — free tier is 1000 req/month

Ablauf

Run a search with the cheapest provider first

Search Tavily for 'latest MCP protocol changes 2026'. Summarize the top 5 results.✓ Kopiert

→ Summary with citations
Cross-check on a different provider

Now search the same query on Brave. Which results show up in both? Which are unique?✓ Kopiert

→ Overlap analysis
Extract full content for the most promising result

Use web_extract on the top result and give me the actual useful text, not nav boilerplate.✓ Kopiert

→ Clean markdown of the article

Ergebnis: A cross-validated research answer with confidence boosted by multi-engine agreement.

Fallstricke

Per-provider quotas vary — Tavily is generous, Kagi costs per query — Route exploratory searches to Tavily, save Kagi for high-signal 'give me the answer' queries via FastGPT
web_extract fails on JS-heavy sites — Use Firecrawl (JS-rendering) for SPAs; Tavily extract for static pages

Kombinieren mit: notion

Get a cited quick answer with AI search

👤 Anyone who wants 'what's the answer' not 'here are 10 blue links' ⏱ ~5 min beginner

Wann einsetzen: A specific factual question where you want reasoning with sources.

Voraussetzungen

At least one AI-search key: KAGI_API_KEY, EXA_API_KEY, or LINKUP_API_KEY — Kagi FastGPT is the cheapest per query

Ablauf

Ask via ai_search

Use ai_search (Kagi FastGPT) for: what's the default rate limit for the GitHub Models API as of Q1 2026?✓ Kopiert

→ Direct answer with citations
Verify the citation

Open the top citation with web_extract and confirm the claim.✓ Kopiert

→ Quoted source text

Ergebnis: A verified quick answer, cheaper and faster than a free-search round-trip.

Fallstricke

AI search can confidently misquote sources — Always web_extract the top citation for claims that matter

Search public GitHub for reference implementations

👤 Devs evaluating libraries or looking for code patterns ⏱ ~15 min intermediate

Wann einsetzen: 'Has anyone solved X in Rust?' type questions.

Voraussetzungen

GITHUB_API_KEY with no scopes (public only) — github.com/settings/tokens — classic token with empty scope list is fine

Ablauf

Search with code operators

github_search for fn main() language:rust path:src/ 'tokio::select!' — top 20 repos.✓ Kopiert

→ Repo list with file hits
Pull specific files worth reading

For the top 3 hits, use web_extract on the raw.githubusercontent URLs and show me the tokio::select! patterns they use.✓ Kopiert

→ Code excerpts with context

Ergebnis: A focused reading list of real-world implementations you can learn from.

Kombinieren mit: github

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

omnisearch + notion

Research a topic across engines, save distilled notes to Notion

Research 'post-quantum TLS 2026 state of play' across Tavily and Brave, extract the 3 best sources, and save a Notion page summarizing them.✓ Kopiert

omnisearch + github

Discover repos on GitHub public search, then do deep ops on the best one via the github MCP

github_search for rate-limiter libraries in Go, pick the top, then via the github MCP open its latest 3 issues.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
web_search	query: str, provider?: tavily\|brave\|kagi\|exa, options?: {site?, filetype?, time?, lang?}	Broad web search with operator control	1 provider API call
ai_search	query: str, provider?: kagi_fastgpt\|exa\|linkup	You want a direct cited answer, not links	1 AI-search call (costlier than regular search)
github_search	query: str, kind?: code\|repo\|user	Code/repo/user discovery with GitHub syntax	1 GitHub API call (30/min code search limit)
web_extract	url: str, provider?: firecrawl\|tavily\|kagi	Get clean article text from a URL	1 extractor call

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: Per-provider. Tavily: 1000 req/mo free. Brave: 2000/mo free. Kagi: pay-per-call. Exa: free tier ~1000/mo.
Tokens pro Aufruf: Search results: 500-1500 tokens. AI search with citations: 1-3k. Extracted articles: 2-8k.
Kosten in €: Free to start (Tavily, Brave, Exa free tiers); Kagi pay-per-call; Firecrawl self-host = free
Tipp: Route: cheap broad search → Tavily/Brave; high-signal answers → Kagi FastGPT; extraction → self-hosted Firecrawl.

Sicherheit

Rechte, Secrets, Reichweite

Minimale Scopes: GitHub token: empty scopes (public only)

Credential-Speicherung: Env vars per provider: TAVILY_API_KEY, BRAVE_API_KEY, etc.

Datenabfluss: Queries to each configured provider's API; results back through

Niemals gewähren: GitHub token with repo write — web_search is public-only Self-hosted Firecrawl without auth exposed to public internet

Each provider's TOS applies to your usage — don't scrape with one, extract with another, and re-publish.
Providers log queries. Don't search for secrets or internal-only terms.

Fehlerbehebung

Häufige Fehler und Lösungen

Provider not configured

Set the env var for that provider, or pass provider= to route to a different one.

Prüfen: echo $TAVILY_API_KEY

Firecrawl extraction timeout

Heavy SPA; raise FIRECRAWL timeout, or fall back to tavily/kagi extract for static pages.

GitHub search returns 403

Unauthenticated code search is heavily rate-limited. Supply GITHUB_API_KEY even with empty scopes.

Prüfen: curl -H 'Authorization: Bearer $GITHUB_API_KEY' https://api.github.com/rate_limit

Alternativen

mcp-omnisearch vs. andere

Alternative	Wann stattdessen	Kompromiss
brave-search MCP	You only need one engine and want a minimal config	No AI search, no multi-provider redundancy
searxng MCP	You want fully self-hosted metasearch with no API keys	You host the SearXNG instance
kindly-web-search	You want fuller content retrieval baked in (full StackOverflow threads, GitHub issues)	Smaller provider list

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen