MCP server for integrating Omnisearch with LLMs
MCPpedia last refreshed this data
MCP server for integrating Omnisearch with LLMs is an MCP server that MCP server for integrating Omnisearch with LLMs. Its tool list has not been published yet over stdio and http, requires no API key, and scores 88/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"mcp-omnisearch": {
"env": {
"EXA_API_KEY": "your-exa-key",
"KAGI_API_KEY": "your-kagi-key",
"BRAVE_API_KEY": "your-brave-key",
"GITHUB_API_KEY": "your-github-key",
"LINKUP_API_KEY": "your-linkup-key",
"TAVILY_API_KEY": "your-tavily-key",
"FIRECRAWL_API_KEY": "your-firecrawl-key",
"FIRECRAWL_BASE_URL": "http://localhost:3002"
},
"args": [
"/path/to/mcp-omnisearch/dist/index.js"
],
"command": "node",
"disabled": false,
"autoApprove": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for integrating Omnisearch with LLMs
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y 'mcp-omnisearch' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked mcp-omnisearch against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in search
Open-source web scraper for AI agents with scrape, crawl, and map tools
MCP server for advanced web search using Tavily
MCP server for enterprise local codebase indexing, semantic search, and code dependency graphs.
The official MCP server implementation for the Perplexity API Platform
MCP Security Weekly
Get CVE alerts and security updates for MCP server for integrating Omnisearch with LLMs and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server for Tavily, Brave, Kagi, Exa,
GitHub, Linkup, and Firecrawl. Two tools, search and execute,
expose schema-generated native provider functions through Pi's local
QuickJS sandbox. Requires Node.js 22.19+.
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.
searchDiscover available functions and their compact TypeScript declarations. A provider-scoped lookup returns names and schemas together:
{ "query": "tavily" }
Use an exact name such as tavily_search for a smaller lookup, or
{} for a catalog without declarations. Only configured providers
appear.
executeRun JavaScript against the discovered native provider functions:
{
"code": "const r = await tools.tavily_search({ query: 'MCP code mode', max_results: 3 }); return r.results.map(({ title, url }) => ({ title, url }));"
}
Compose calls with await and Promise.all, filter intermediate
data, and return only what the client needs. Credentials stay on the
host; the sandbox has no filesystem or arbitrary network access.
Arguments and responses use native provider formats, not a normalized
search contract. See
Code Mode
for functions, limits and benchmark findings.
The consolidated web_search, ai_search, web_extract and
github_search tools have been removed. Provider keys stay the same,
but existing tool calls and client instructions need migration. See
the
breaking-change migration guide.