mcp-omnisearch

Overview

mcp-omnisearch is a comprehensive MCP server that consolidates multiple search providers and AI tools into four main functions: web search, AI-powered answers, GitHub search, and content extraction. It supports providers like Tavily, Brave, Kagi, Exa, GitHub, Linkup, and Firecrawl. The server is flexible, allowing users to start with just one or two API keys and add more as needed, making it easy to get started while offering advanced capabilities for power users.

Try asking AI

After installing, here are 6 things you can ask your AI assistant:

• web_search

  Search the web for information using multiple providers.

  Try:Search for the latest developments in quantum computingTry:Find information about rust programming language features on GitHubTry:Search for the latest AI research papers on arxiv.org
• ai_search

  Get AI-powered answers with citations and reasoning.

  Try:Explain the differences between REST and GraphQLTry:How does machine learning work?Try:What are the latest advances in quantum computing?
• github_search

  Search GitHub for code, repositories, or users.

  Try:Find remote.ts files in sveltejs/kit repositoryTry:Search for sveltekit remote function repositories sorted by starsTry:Find user profiles for Rich-Harris
• web_extract

  Extract, process, or summarize web content from URLs.

  Try:Extract content from https://example.com/long-articleTry:Summarize the content at https://example.com/video-page using KagiTry:Scrape https://example.com/blog using Firecrawl

Comparable tools

Installation

{
  "mcpServers": {
    "mcp-omnisearch": {
      "command": "node",
      "args": ["/path/to/mcp-omnisearch/dist/index.js"],
      "env": {
        "TAVILY_API_KEY": "your-tavily-key",
        "KAGI_API_KEY": "your-kagi-key",
        "BRAVE_API_KEY": "your-brave-key",
        "GITHUB_API_KEY": "your-github-key",
        "EXA_API_KEY": "your-exa-key",
        "LINKUP_API_KEY": "your-linkup-key",
        "FIRECRAWL_API_KEY": "your-firecrawl-key",
        "FIRECRAWL_BASE_URL": "http://localhost:3002"
      }
    }
  }
}

FAQ

Do I need API keys for all providers?

No, the server automatically detects which API keys are available and only enables those providers. You can start with just one or two keys and add more as needed.

How do I handle large search results?

You can configure the server with OMNISEARCH_LARGE_RESULT_MODE environment variable ('file' or 'inline'). Individual tools can also override this setting with a 'large_result_mode' parameter.

Compare mcp-omnisearch with