Omnisearch MCP server
MCP server for integrating Omnisearch with LLMs
350 stars470 downloads/wk
Reviews
Write oneNobody has reviewed Omnisearch yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Omnisearch tools (3)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
github_repository_searchSearch for repositories on GitHub
github_searchSearch for code on GitHub. This is ideal for finding code examples, tracking down function definitions, or locating files with specific names or paths. Supports advanced query syntax with qualifiers like `filename:`, `path:`, `repo:`, `user:`, `language:`, and `in:file`. For example, to find a file named `settings.json` in a `.claude` directory, you could use the query: `filename:settings.json pat
github_user_searchSearch for users and organizations on GitHub
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
- Code scan56 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Install Omnisearch in Claude Code, Cursor or VS Code
Runs npx -y mcp-omnisearch on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-omnisearch -- npx -y mcp-omnisearch
What the publisher says
From the Omnisearch repository's README, as published. We do not edit it. Read it on GitHub
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-omnisearchMCPick 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 projectSee Deployment for supported clients and provider credential storage options.
To run from source instead:
pnpm install
pnpm run build
node ./dist/index.jsProviders 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
web_search
Search the web with Tavily, Brave, Kagi, Exa, or Kagi Enrichment.
{
"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.
ai_search
Get sourced AI answers with Kagi FastGPT, 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": "kagi_fastgpt"
}github_search
Search GitHub code, repositories, or users.
{
"query": "filename:remote.ts @sveltejs/kit",
"search_type": "code",
"limit": 5
}web_extract
Extract, crawl, scrape, summarize, or find similar content with Tavily, Kagi, 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
by task, key, mode, and capability.
- Provider selection — choose providers
matrix and tested examples.
- Search operators — operator support
behavior and remote deployment caveats.
- Large results — inline vs file response
setup.
- Deployment — MCP client, WSL, and Firecrawl
validation, rate limits, and common failures.
- Troubleshooting — keys, access,
Environment variables
- TAVILYAPIKEY
- KAGIAPIKEY
- BRAVEAPIKEY
- GITHUBAPIKEY
- EXAAPIKEY
- LINKUPAPIKEY
- FIRECRAWLAPIKEY
- FIRECRAWLBASEURL optional, for self-hosted Firecrawl
- OMNISEARCHLARGERESULT_MODE optional, file default or inline
Development
pnpm install
pnpm run build
pnpm testShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Omnisearch: common questions
- Is Omnisearch MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Omnisearch safety report
- How do I install Omnisearch?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Omnisearch need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Omnisearch maintained?
- The last commit was 12 days ago (2026-10-01). The latest release is v0.0.15.