This Model Context Protocol (MCP) server integrates Omnisearch with LLMs by providing unified access to external search and crawling services. It consolidates access to Tavily, Brave, Kagi, Exa AI, GitHub, Linkup, and Firecrawl through four tools, as described in its README excerpt.
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+.
See
Deployment
for supported clients and provider credential storage options.
To run from source instead:
bash
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:
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
Discover available functions and their compact TypeScript
declarations. A provider-scoped lookup returns names and schemas
together:
json
{"query":"tavily"}
Use an exact name such as tavily_search for a smaller lookup, or
{} for a catalog without declarations. Only configured providers
appear.
execute
Run JavaScript against the discovered native provider functions:
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.
Upgrading
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.
Documentation
Migration
ā move from consolidated tools to Code Mode.
Code Mode
ā native provider functions, schema generation, local testing, and
benchmark findings.
Provider selection
ā choose providers by task, key, mode, and capability.
Search operators
ā native query syntax and provider-specific filters.
Large results
ā inline vs file response behavior and remote deployment caveats.
Deployment
ā MCP client, WSL, and Firecrawl setup.
Troubleshooting
ā keys, access, validation, rate limits, and common failures.
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