spences10/mcp-omnisearch

pnpm install
pnpm run build
node ./dist/index.js

Usage

• •Configure the server in an MCP client with whichever provider API keys you hold; providers without keys are skipped and the rest keep working
• •web_search: search with Tavily, Brave, Kagi, Exa, or Kagi Enrichment
• •ai_search: sourced AI answers via Kagi FastGPT, Exa Answer, or Linkup
• •web_extract: extract, crawl, scrape, summarize, or find similar content with Tavily, Kagi, Firecrawl, or Exa

Key features

• ✓Four consolidated tools covering search, AI answers, GitHub code/repo/user search, and page extraction across seven providers
• ✓Provider fallback: keys are optional, missing providers are skipped automatically
• ✓Environment-driven config (TAVILY_API_KEY, KAGI_API_KEY, BRAVE_API_KEY, GITHUB_API_KEY, EXA_API_KEY, LINKUP_API_KEY, FIRECRAWL_API_KEY)
• ✓Optional FIRECRAWL_BASE_URL for self-hosted Firecrawl; OMNISEARCH_LARGE_RESULT_MODE for inline vs file responses
• ✓Docs for provider selection, search operators, large results, deployment (WSL/Docker/cloud), and troubleshooting

Best for

Agents that need multi-provider web search and extraction with automatic fallback between commercial search APIs.

Caveats

• ⚠Requires at least one provider API key to be useful
• ⚠Build from source with pnpm before running (no published prebuilt binary mentioned in README)