S
spences10/mcp-omnisearch
Search via Tavily, Brave, Kagi and Exa
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
- 复制上面的命令
- 粘成
claude_desktop_config.json里mcpServers的一项(本地服务器用 command + args,示例见 客户端接法) - 重启客户端
客户端配置(取自该仓库的安装命令)
{
"mcpServers": {
"spences10-mcp-omnisearch": {
"command": "npx",
"args": ["-y", "mcp-omnisearch"]
}
}
}解析自我们于 2026-11-07 抓取的该仓库 README;我们未执行过。
command/args 来自仓库写明的安装命令;不确定时请以该项目 README 为准。
VS Code(.vscode/mcp.json —— 键名是 servers)
{
"servers": {
"spences10-mcp-omnisearch": {
"command": "npx",
"args": ["-y", "mcp-omnisearch"]
}
}
}VS Code 顶层键是 <code>servers</code>,其余与上面那份相同。
Claude Code(命令行)
claude mcp add --transport stdio spences10-mcp-omnisearch -- npx -y mcp-omnisearch
Claude Code 不收 JSON 文件,用这条命令直接加。
配置项的键名以你的客户端为准:客户端与 CLI
- 来源明细
- 收录自 abordage/awesome-mcp 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-05 · 最近见到 2026-11-14 · 共见到 10 次 · 被 10 个来源列出
- 评分构成
- 综合分 1,003 · 10 个来源 · mcp
- 安装
npx -y mcp-omnisearch
常见问题(答案都来自我们的记录)
怎么安装?
该仓库给出的安装命令是
npx -y mcp-omnisearch。我们的记录里它是仓库自己提供的;不保证在你的客户端上直接可用。它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
我们收录于 2026-11-05;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
# mcp-omnisearch
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
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+.
## Quick start
Install the published server with
MCPick:
bash
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:
bash
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:
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:
json
"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
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:
json
"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.
## 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
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+.
## Quick start
Install the published server with
MCPick:
bash
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:
bash
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:
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:
json
"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
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:
json
"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.
## 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
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/spences10-mcp-omnisearch/)
- 来源
- awesome · https://github.com/spences10/mcp-omnisearch
- 按领域浏览
- MCP 服务
- 收录来源
- 10 个独立来源
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。