io.github.spences10/mcp-omnisearch

Official registry Other

MCP server for integrating Omnisearch with LLMs

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package mcp-omnisearch
Claude Code
claude mcp add mcp-omnisearch -- npx -y mcp-omnisearch@0.0.15
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "mcp-omnisearch": {
            "command": "npx",
            "args": [
                "-y",
                "mcp-omnisearch@0.0.15"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-omnisearch
  2. Quick start
  3. Tools
  4. Documentation
  5. Environment variables
  6. Development
  7. License
  8. Acknowledgments

mcp-omnisearch

A Model Context Protocol (MCP) server that provides unified access to Tavily, Brave, Kagi, Exa AI, GitHub, Linkup, and Firecrawl through four consolidated tools.

Quick start

Install the published server with MCPick:

npx mcpick add \
  --name mcp-omnisearch \
  --command npx \
  --args=-y,mcp-omnisearch

MCPick defaults to Claude Code. Use --client and --scope to target another client or add the server to the current repository:

npx mcpick add \
  --name mcp-omnisearch \
  --command npx \
  --args=-y,mcp-omnisearch \
  --client vscode \
  --scope project

See Deployment for supported clients and provider credential storage options.

To run from source instead:

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

Providers without keys are skipped and the rest keep working. If your client supports environment-variable expansion, reference keys instead of storing their values in the MCP configuration:

{
    "mcpServers": {
        "mcp-omnisearch": {
            "command": "npx",
            "args": ["-y", "mcp-omnisearch"],
            "env": {
                "TAVILY_API_KEY": "${TAVILY_API_KEY}",
                "EXA_API_KEY": "${EXA_API_KEY}"
            }
        }
    }
}

Add only the provider keys you use. Expansion syntax and secret storage are client-specific; see Deployment for secure options and plaintext fallback guidance.

Tools

Search the web with Tavily, Brave, Kagi, or Exa.

{
    "query": "latest SvelteKit releases",
    "provider": "tavily",
    "limit": 10,
    "search_depth": "advanced",
    "topic": "news",
    "time_range": "month",
    "safe_search": true,
    "include_raw_content": false,
    "auto_parameters": false
}

Search controls apply when supported by the selected provider.

Get sourced AI answers with Exa Answer, Linkup, or Tavily Research. Tavily Research returns a task ID first; pass it back as research_id to retrieve the report.

{
    "query": "Explain the differences between REST and GraphQL",
    "provider": "exa_answer"
}

Search GitHub code, repositories, or users.

{
    "query": "filename:remote.ts @sveltejs/kit",
    "search_type": "code",
    "limit": 5
}
web_extract

Extract, crawl, scrape, or find similar content with Tavily, Firecrawl, or Exa.

{
    "url": "https://example.com/long-article",
    "provider": "tavily",
    "mode": "extract",
    "extract_depth": "advanced",
    "query": "installation requirements",
    "chunks_per_source": 3,
    "format": "markdown"
}

Documentation

Environment variables

  • TAVILY_API_KEY
  • KAGI_API_KEY
  • BRAVE_API_KEY
  • GITHUB_API_KEY
  • EXA_API_KEY
  • LINKUP_API_KEY
  • FIRECRAWL_API_KEY
  • FIRECRAWL_BASE_URL optional, for self-hosted Firecrawl
  • OMNISEARCH_LARGE_RESULT_MODE optional, file default or inline

Development

pnpm install
pnpm run build
pnpm test

Please read CONTRIBUTING.md before opening a PR.

License

MIT License - see LICENSE.

Acknowledgments

Built on Model Context Protocol, Tavily, Kagi, Brave Search, Exa AI, Linkup, and Firecrawl.

Frequently asked questions

What is io.github.spences10/mcp-omnisearch?

MCP server for integrating Omnisearch with LLMs

How do I install io.github.spences10/mcp-omnisearch?

It runs on your machine. In Claude Code: claude mcp add mcp-omnisearch -- npx -y mcp-omnisearch@0.0.15. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.spences10/mcp-omnisearch need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.spences10/mcp-omnisearch open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.spences10/mcp-omnisearch?

It is published by spences10. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.