de en es ja ko ru zh

mcp-omnisearch

Name: mcp-omnisearch
Author: spences10

by spences10

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

mcp-omnisearch

一个模型上下文协议 (MCP) 服务器，提供对多个搜索提供商和 AI 工具的统一访问。该服务器整合了 Tavily、Perplexity、Kagi、Jina AI、Brave 和 Firecrawl 的功能，通过单一界面提供全面的搜索、AI 响应、内容处理和增强功能。

特征

🔍 搜索工具

Tavily Search ：针对事实信息进行了优化，并提供强大的引用支持。支持通过 API 参数 (include_domains/exclude_domains) 进行域名过滤。
Brave Search ：注重隐私的搜索，涵盖广泛的技术内容。原生支持搜索运算符（site:、-site:、filetype:、intitle:、inurl:、before:、after: 和精确短语）。
Kagi 搜索：高质量搜索结果，广告影响极小，专注于权威来源。支持查询字符串中的搜索运算符（site:、-site:、filetype:、intitle:、inurl:、before:、after: 和精确短语）。

🎯 搜索运算符

MCP Omnisearch通过操作符和参数提供了强大的搜索功能：

常见搜索功能

域名过滤：所有提供商均可使用
- Tavily：通过 API 参数（include_domains/exclude_domains）
- Brave & Kagi：通过 site: 和 -site: 运算符
文件类型过滤：Brave 和 Kagi 中可用（filetype:）
标题和 URL 过滤：Brave 和 Kagi 中可用（intitle:、inurl:）
日期过滤：Brave 和 Kagi 中可用（之前：、之后：）
精确短语匹配：在 Brave 和 Kagi（“短语”）中可用

示例用法

// Using Brave or Kagi with query string operators
{
  "query": "filetype:pdf site:microsoft.com typescript guide"
}

// Using Tavily with API parameters
{
  "query": "typescript guide",
  "include_domains": ["microsoft.com"],
  "exclude_domains": ["github.com"]
}

提供商能力

Brave Search ：查询字符串中完全支持本机运算符
Kagi 搜索：查询字符串中完整的运算符支持
Tavily Search ：通过 API 参数进行域名过滤

🤖 AI 响应工具

Perplexity AI ：将实时网络搜索与 GPT-4 Omni 和 Claude 3 相结合的高级响应生成
Kagi FastGPT ：AI 快速生成带引文的答案（典型响应时间为 900 毫秒）

📄内容处理工具

Jina AI 阅读器：清晰地提取内容，并支持图片说明和 PDF 文件
Kagi Universal Summarizer ：页面、视频和播客的内容摘要
Tavily Extract ：从单个或多个网页中提取原始内容，并可配置提取深度（“基本”或“高级”）。返回合并内容和单个 URL 内容，以及包含字数统计和提取统计信息的元数据。
Firecrawl Scrape ：使用增强的格式选项从单个 URL 中提取干净的、LLM 就绪的数据
Firecrawl Crawl ：深度抓取网站上所有可访问的子页面，并设置深度限制
Firecrawl Map ：快速从网站收集 URL，进行全面的站点映射
Firecrawl Extract ：利用自然语言提示进行 AI 结构化数据提取
Firecrawl 操作：支持提取动态内容之前的页面交互（点击、滚动等）

🔄 增强工具

Kagi Enrichment API ：来自专业索引的补充内容（Teclis、TinyGem）
Jina AI Grounding ：针对网络知识的实时事实验证

Related MCP server: MCP Search Server

灵活的 API 密钥要求

MCP Omnisearch 旨在与您现有的 API 密钥配合使用。您无需拥有所有提供商的密钥 - 服务器会自动检测哪些 API 密钥可用，并仅启用这些提供商的密钥。

例如：

如果您只有 Tavily 和 Perplexity API 密钥，则只有这些提供商可用
如果您没有 Kagi API 密钥，基于 Kagi 的服务将不可用，但所有其他提供商将正常运行
服务器将根据您配置的 API 密钥记录可用的提供商

这种灵活性使得只需一个或两个提供商即可轻松开始，并根据需要添加更多提供商。

配置

此服务器需要通过您的 MCP 客户端进行配置。以下是不同环境的示例：

克莱恩配置

将其添加到您的 Cline MCP 设置中：

{
	"mcpServers": {
		"mcp-omnisearch": {
			"command": "node",
			"args": ["/path/to/mcp-omnisearch/dist/index.js"],
			"env": {
				"TAVILY_API_KEY": "your-tavily-key",
				"PERPLEXITY_API_KEY": "your-perplexity-key",
				"KAGI_API_KEY": "your-kagi-key",
				"JINA_AI_API_KEY": "your-jina-key",
				"BRAVE_API_KEY": "your-brave-key",
				"FIRECRAWL_API_KEY": "your-firecrawl-key"
			},
			"disabled": false,
			"autoApprove": []
		}
	}
}

带有 WSL 配置的 Claude 桌面

对于 WSL 环境，将其添加到您的 Claude Desktop 配置中：

{
	"mcpServers": {
		"mcp-omnisearch": {
			"command": "wsl.exe",
			"args": [
				"bash",
				"-c",
				"TAVILY_API_KEY=key1 PERPLEXITY_API_KEY=key2 KAGI_API_KEY=key3 JINA_AI_API_KEY=key4 BRAVE_API_KEY=key5 FIRECRAWL_API_KEY=key6 node /path/to/mcp-omnisearch/dist/index.js"
			]
		}
	}
}

环境变量

服务器会为每个提供商使用 API 密钥。您不需要所有提供商的密钥- 仅激活与您可用 API 密钥对应的提供商：

TAVILY_API_KEY ：用于 Tavily 搜索
PERPLEXITY_API_KEY ：用于 Perplexity AI
KAGI_API_KEY ：用于 Kagi 服务（FastGPT、Summarizer、Enrichment）
JINA_AI_API_KEY ：用于 Jina AI 服务（Reader、Grounding）
BRAVE_API_KEY ：用于 Brave 搜索
FIRECRAWL_API_KEY ：用于 Firecrawl 服务（抓取、抓取、映射、提取、操作）

您可以先使用一两个 API 密钥，之后再根据需要添加更多密钥。服务器将在启动时记录可用的提供程序。

API

服务器实现按类别组织的 MCP 工具：

搜索工具

搜索_塔维利

使用 Tavily Search API 搜索网页。最适合需要可靠来源和引文的事实性查询。

参数：

query （字符串，必需）：搜索查询

例子：

{
	"query": "latest developments in quantum computing"
}

search_brave

注重隐私的网络搜索，对技术主题有很好的覆盖。

参数：

query （字符串，必需）：搜索查询

例子：

{
	"query": "rust programming language features"
}

搜索_kagi

高质量搜索结果，广告影响极小。最适合查找权威来源和研究资料。

参数：

query （字符串，必需）：搜索查询
language （字符串，可选）：语言过滤器（例如“en”）
no_cache （布尔值，可选）：绕过缓存以获得最新结果

例子：

{
	"query": "latest research in machine learning",
	"language": "en"
}

AI响应工具

ai_perplexity

通过实时网络搜索集成实现人工智能响应生成。

参数：

query （字符串，必需）：AI 响应的问题或主题

例子：

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

ai_kagi_fastgpt

快速 AI 生成带有引文的答案。

参数：

query （字符串，必需）：用于快速 AI 响应的问题

例子：

{
	"query": "What are the main features of TypeScript?"
}

内容处理工具

process_jina_reader

将 URL 转换为带有图像字幕的干净、LLM 友好的文本。

参数：

url （字符串，必需）：要处理的 URL

例子：

{
	"url": "https://example.com/article"
}

process_kagi_summarizer

从 URL 中总结内容。

参数：

url （字符串，必需）：要汇总的 URL

例子：

{
	"url": "https://example.com/long-article"
}

process_tavily_extract

使用 Tavily Extract 从网页中提取原始内容。

参数：

url (string | string[]，必需)：用于从中提取内容的单个 URL 或 URL 数组
extract_depth （字符串，可选）：提取深度 - “基本”（默认）或“高级”

例子：

{
	"url": [
		"https://example.com/article1",
		"https://example.com/article2"
	],
	"extract_depth": "advanced"
}

响应包括：

所有 URL 的组合内容
每个 URL 的单独原始内容
包含字数、成功提取和任何失败 URL 的元数据

firecrawl_scrape_process

使用增强的格式化选项从单个 URL 中提取干净的、LLM 就绪的数据。

参数：

url (string | string[]，必需)：用于从中提取内容的单个 URL 或 URL 数组
extract_depth （字符串，可选）：提取深度 - “基本”（默认）或“高级”

例子：

{
	"url": "https://example.com/article",
	"extract_depth": "basic"
}

响应包括：

干净的 Markdown 格式内容
元数据包括标题、字数和提取统计数据

firecrawl_crawl_process

对网站上所有可访问的子页面进行深度抓取，并设置深度限制。

参数：

url (string | string[]，必填)：抓取的起始 URL
extract_depth （字符串，可选）：提取深度 - “基本”（默认）或“高级”（控制爬行深度和限制）

例子：

{
	"url": "https://example.com",
	"extract_depth": "advanced"
}

响应包括：

所有已抓取页面的合并内容
每个页面的单独内容
元数据包括标题、字数和抓取统计数据

firecrawl_map_process

快速从网站收集 URL，以进行全面的站点映射。

参数：

url (string | string[]，必需)：要映射的 URL
extract_depth （字符串，可选）：提取深度 - “基本”（默认）或“高级”（控制地图深度）

例子：

{
	"url": "https://example.com",
	"extract_depth": "basic"
}

响应包括：

所有发现的 URL 列表
元数据包括网站标题和 URL 数量

firecrawl_extract_process

使用自然语言提示通过人工智能提取结构化数据。

参数：

url (string | string[]，必需)：从中提取结构化数据的 URL
extract_depth （字符串，可选）：提取深度 - “基本”（默认）或“高级”

例子：

{
	"url": "https://example.com",
	"extract_depth": "basic"
}

响应包括：

从页面中提取的结构化数据
元数据包括标题、提取统计数据

firecrawl_actions_process

支持提取动态内容之前的页面交互（点击、滚动等）。

参数：

url (string | string[]，必需)：用于交互和提取内容的 URL
extract_depth （字符串，可选）：提取深度 - “基本”（默认）或“高级”（控制交互的复杂性）

例子：

{
	"url": "https://news.ycombinator.com",
	"extract_depth": "basic"
}

响应包括：

执行交互后提取的内容
所执行操作的描述
页面截图（如有）
元数据包括标题和提取统计数据

增强工具

增强_kagi_enrichment

从专门的索引中获取补充内容。

参数：

query （字符串，必需）：查询丰富内容

例子：

{
	"query": "emerging web technologies"
}

增强_jina_grounding

根据网络知识验证陈述。

参数：

statement （字符串，必需）：要验证的语句

例子：

{
	"statement": "TypeScript adds static typing to JavaScript"
}

发展

设置

克隆存储库
安装依赖项：

pnpm install

构建项目：

pnpm run build

以开发模式运行：

pnpm run dev

出版

更新 package.json 中的版本
构建项目：

pnpm run build

发布到 npm：

pnpm publish

故障排除

API 密钥和访问权限

每个提供商都需要自己的 API 密钥，并且可能有不同的访问要求：

Tavily ：需要从其开发者门户获取 API 密钥
困惑：通过开发者程序访问 API
Kagi ：某些功能仅限于商业（团队）计划用户使用
Jina AI ：所有服务都需要 API 密钥
Brave ：来自其开发者门户的 API 密钥
Firecrawl ：需要从其开发者门户获取 API 密钥

速率限制

每个提供商都有各自的速率限制。服务器会妥善处理速率限制错误并返回相应的错误消息。

贡献

欢迎贡献代码！欢迎提交 Pull 请求。

执照

MIT 许可证 - 有关详细信息，请参阅LICENSE文件。

致谢

构建于：

Available Tools

3 tools

ai_searchGet AI-powered answers with citations and reasoning. Use when you need synthesized answers rather than raw search results. Providers: kagi_fastgpt (fast answers), exa_answer (semantic AI), linkup (deep agentic search), tavily_research (asynchronous multi-search reports; resubmit its research_id to retrieve results).B

Read-onlyIdempotent

Get AI-powered answers with citations and reasoning. Use when you need synthesized answers rather than raw search results. Providers: kagi_fastgpt (fast answers), exa_answer (semantic AI), linkup (deep agentic search), tavily_research (asynchronous multi-search reports; resubmit its research_id to retrieve results).

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results (default: 10)
`query`	Yes	Search query
`provider`	Yes	AI search provider to use
`research_id`	No	Existing asynchronous research task ID to retrieve. Supported by Tavily Research.
`large_result_mode`	No	How to handle oversized responses for this request. Use inline for remote/container transports; file is local shared-filesystem behavior. Defaults to OMNISEARCH_LARGE_RESULT_MODE or file.

TDQS

B3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only/idempotent safety, so the description adds value by disclosing asynchronous retrieval behavior for tavily_research ('resubmit its research_id'), provider-specific behaviors, and the output nature (citations and reasoning). No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with the purpose front-loaded and provider details compactly listed. Every clause contributes meaning without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers when-to-use, provider differences, and the async resubmission pattern, and annotations cover safety. However, it omits response structure and contains a provider/enum inconsistency, leaving an agent with an ambiguous picture for a 5-parameter tool without an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the description need not repeat parameter details, but it adds provider characteristics that conflict with the enum by naming exa_answer and linkup which are not valid values. It does usefully explain research_id for Tavily, but the misinformation undermines reliability.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tautological: description restates name/title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use when you need synthesized answers rather than raw search results', giving a clear when-to-use signal. However, it lists exa_answer and linkup as providers even though the schema enum only allows kagi_fastgpt and tavily_research, making the provider-selection guidance partially misleading.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

web_extractExtract, process, or summarize web content from URLs. Use when you need to read page content, summarize articles, crawl sites, or extract structured data. Providers: tavily (content extraction), kagi (summarization of pages/videos/podcasts), firecrawl (scraping/crawling/mapping/structured extraction/interactive), exa (content retrieval/similar pages).B

Read-onlyIdempotent

Extract, process, or summarize web content from URLs. Use when you need to read page content, summarize articles, crawl sites, or extract structured data. Providers: tavily (content extraction), kagi (summarization of pages/videos/podcasts), firecrawl (scraping/crawling/mapping/structured extraction/interactive), exa (content retrieval/similar pages).

ParametersJSON Schema

Name	Required	Description
`url`	Yes	URL or array of URLs to process
`mode`	No	Processing mode. Firecrawl: scrape/crawl/map/extract/actions. Exa: contents/similar. Tavily: extract/crawl/map. Kagi: summarize. Defaults to provider default.
`query`	No	Focus extracted content on information relevant to this query.
`format`	No	Extracted page format (default: markdown).
`provider`	Yes	Processing provider to use
`extract_depth`	No	Extraction depth (default: basic)
`chunks_per_source`	No	Maximum relevant content chunks per source when a query is provided.
`large_result_mode`	No	How to handle oversized responses for this request. Use inline for remote/container transports; file is local shared-filesystem behavior. Defaults to OMNISEARCH_LARGE_RESULT_MODE or file.
`include_raw_contents`	No	Whether extraction responses should include per-URL raw_contents alongside combined content (default: true).

TDQS

B3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds provider capability context (e.g., firecrawl for scraping/crawling/interactive, kagi for summarization). However, the mention of 'exa' as a provider is misleading because the input schema's provider enum omits exa, creating uncertainty about available behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact, front-loads the purpose, and packs useful provider information into a short list. Minor redundancy ('process' with 'extract') and the misleading exa reference are the only blemishes; overall it earns its length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter tool with 5 enums and provider-specific modes, the description is too thin. It does not explain how to choose a provider for a given task, what the different modes do relative to providers, or how to handle edge cases like exa's absence from the provider enum. There is no output schema, and the description gives no hint about return value shapes, so an agent would likely need to infer provider-mode compatibility.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the parameters are fully documented in the schema. The description adds value by loosely mapping providers to capabilities (e.g., kagi for summarization, firecrawl for scraping), which helps select provider and mode. But it introduces a conflict by listing exa although the provider enum does not include it, and it does not explain the relationship between provider and mode beyond the parentheticals.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tautological: description restates name/title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit 'Use when...' conditions covering the main scenarios, and the provider list gives a starting point for mode selection. It does not state when not to use this tool or point to alternatives like web_search or ai_search, so it lacks explicit exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

web_searchSearch the web for information. Use when you need to find web pages, articles, or data. Providers: tavily (factual/citations and search controls), brave (privacy/operators), kagi (quality/operators), exa (AI-semantic), kagi_enrichment (specialized indexes). Search depth, topic, time range, safe search, raw content, and automatic parameters apply when supported by the provider.B

Read-onlyIdempotent

Search the web for information. Use when you need to find web pages, articles, or data. Providers: tavily (factual/citations and search controls), brave (privacy/operators), kagi (quality/operators), exa (AI-semantic), kagi_enrichment (specialized indexes). Search depth, topic, time range, safe search, raw content, and automatic parameters apply when supported by the provider.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results (default: 10)
`query`	Yes	Search query
`topic`	No	Search topic category.
`provider`	Yes	Search provider to use
`time_range`	No	Only return results from this recent time range.
`safe_search`	No	Enable provider safe-search filtering.
`search_depth`	No	Search depth. Providers may use this to balance speed, relevance, and cost.
`auto_parameters`	No	Let supported providers select search settings from the query. This can change cost.
`exclude_domains`	No	Exclude results from these domains
`include_domains`	No	Only return results from these domains
`large_result_mode`	No	How to handle oversized responses for this request. Use inline for remote/container transports; file is local shared-filesystem behavior. Defaults to OMNISEARCH_LARGE_RESULT_MODE or file.
`include_raw_content`	No	Include full page content when the selected provider supports it.

TDQS

B3.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already carry the safety profile (readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false), lowering the burden on the description. The description adds useful context that search depth, topic, time range, safe search, raw content, and auto_parameters behave conditionally 'when supported by the provider,' but it does not disclose result-format, citation, pagination, or cost behavior, which would add meaningful transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: purpose appears in the first sentence, usage in the second, and the provider rundown is dense but informative. The title is a verbatim duplicate of the description, which is mildly redundant, but no other space is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 12 parameters, 5 enums, and no output schema, the description carries a heavy burden. It covers purpose, usage context, and provider-specific parameter behavior, but it does not describe the result format or return expectations, and the provider list conflicts with the schema enum. For such a configurable tool, these are meaningful gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, and the description does add meta-information: several parameters (search_depth, topic, time_range, safe_search, raw_content, auto_parameters) are provider-dependent, which is not in the schema. However, the description lists 'exa' as a valid provider while the schema enum omits it, which could mislead an agent into sending an invalid provider value and offset the added value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tautological: description restates name/title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives an explicit when-to-use directive ('Use when you need to find web pages, articles, or data') and adds provider-selection guidance by use case (e.g., tavily for factual/citations, brave for privacy/operators). It does not mention sibling alternatives or state when not to use this tool, stopping short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

3 tool updatesv0.1.0Aug 26, 2026

Changedai_search2 fields changed

changedInput schema / properties / provider / enum

Previous value: -[
-  "kagi_fastgpt"
-]New value: +[
+  "kagi_fastgpt",
+  "tavily_research"
+]

addedInput schema / properties / research_id

Added value: +{
+  "description": "Existing asynchronous research task ID to retrieve. Supported by Tavily Research.",
+  "minLength": 1,
+  "type": "string"
+}

Changedweb_extract5 fields changed

addedInput schema / properties / chunks_per_source

Added value: +{
+  "description": "Maximum relevant content chunks per source when a query is provided.",
+  "maximum": 5,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / format

Added value: +{
+  "description": "Extracted page format (default: markdown).",
+  "enum": [
+    "markdown",
+    "text"
+  ],
+  "type": "string"
+}

changedInput schema / properties / mode / description

Previous value: -"Processing mode. Firecrawl: scrape/crawl/map/extract/actions. Exa: contents/similar. Tavily: extract. Kagi: summarize. Defaults to provider default."New value: +"Processing mode. Firecrawl: scrape/crawl/map/extract/actions. Exa: contents/similar. Tavily: extract/crawl/map. Kagi: summarize. Defaults to provider default."

changedInput schema / properties / mode / enum

Previous value: -[
-  "extract",
-  "summarize",
-  "scrape",
-  "crawl",
-  "map",
-  "actions",
-  "contents",
-  "similar"
-]New value: +[
+  "extract",
+  "crawl",
+  "map",
+  "summarize",
+  "scrape",
+  "actions",
+  "contents",
+  "similar"
+]

addedInput schema / properties / query

Added value: +{
+  "description": "Focus extracted content on information relevant to this query.",
+  "minLength": 1,
+  "pattern": "\\S",
+  "type": "string"
+}

Changedweb_search6 fields changed

addedInput schema / properties / auto_parameters

Added value: +{
+  "description": "Let supported providers select search settings from the query. This can change cost.",
+  "type": "boolean"
+}

addedInput schema / properties / include_raw_content

Added value: +{
+  "description": "Include full page content when the selected provider supports it.",
+  "type": "boolean"
+}

addedInput schema / properties / safe_search

Added value: +{
+  "description": "Enable provider safe-search filtering.",
+  "type": "boolean"
+}

addedInput schema / properties / search_depth

Added value: +{
+  "description": "Search depth. Providers may use this to balance speed, relevance, and cost.",
+  "enum": [
+    "basic",
+    "advanced",
+    "fast",
+    "ultra-fast"
+  ],
+  "type": "string"
+}

addedInput schema / properties / time_range

Added value: +{
+  "description": "Only return results from this recent time range.",
+  "enum": [
+    "day",
+    "week",
+    "month",
+    "year"
+  ],
+  "type": "string"
+}

addedInput schema / properties / topic

Added value: +{
+  "description": "Search topic category.",
+  "enum": [
+    "general",
+    "news",
+    "finance"
+  ],
+  "type": "string"
+}

3 tool updatesv0.0.29Aug 19, 2026

Changedai_search7 fields changed

addedInput schema / properties / large_result_mode

Added value: +{
+  "description": "How to handle oversized responses for this request. Use inline for remote/container transports; file is local shared-filesystem behavior. Defaults to OMNISEARCH_LARGE_RESULT_MODE or file.",
+  "enum": [
+    "inline",
+    "file"
+  ],
+  "type": "string"
+}

addedInput schema / properties / limit / maximum
```
Added value: +50
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

changedInput schema / properties / query / description

Previous value: -"Question or search query"New value: +"Search query"

addedInput schema / properties / query / minLength
```
Added value: +1
```
addedInput schema / properties / query / pattern
```
Added value: +"\\S"
```

Changedweb_extract3 fields changed

addedInput schema / properties / include_raw_contents

Added value: +{
+  "description": "Whether extraction responses should include per-URL raw_contents alongside combined content (default: true).",
+  "type": "boolean"
+}

addedInput schema / properties / large_result_mode

Added value: +{
+  "description": "How to handle oversized responses for this request. Use inline for remote/container transports; file is local shared-filesystem behavior. Defaults to OMNISEARCH_LARGE_RESULT_MODE or file.",
+  "enum": [
+    "inline",
+    "file"
+  ],
+  "type": "string"
+}

changedInput schema / properties / url / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-]New value: +[
+  {
+    "format": "uri",
+    "pattern": "^https?:\\/\\/",
+    "type": "string"
+  },
+  {
+    "items": {
+      "format": "uri",
+      "pattern": "^https?:\\/\\/",
+      "type": "string"
+    },
+    "maxItems": 10,
+    "minItems": 1,
+    "type": "array"
+  }
+]

Changedweb_search10 fields changed

addedInput schema / properties / exclude_domains / items / pattern

Added value: +"^(?:\\*\\.)?(?:[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?\\.)+[a-zA-Z]{2,63}$"

addedInput schema / properties / exclude_domains / maxItems
```
Added value: +20
```

addedInput schema / properties / include_domains / items / pattern

Added value: +"^(?:\\*\\.)?(?:[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?\\.)+[a-zA-Z]{2,63}$"

addedInput schema / properties / include_domains / maxItems
```
Added value: +20
```

addedInput schema / properties / large_result_mode

Added value: +{
+  "description": "How to handle oversized responses for this request. Use inline for remote/container transports; file is local shared-filesystem behavior. Defaults to OMNISEARCH_LARGE_RESULT_MODE or file.",
+  "enum": [
+    "inline",
+    "file"
+  ],
+  "type": "string"
+}

addedInput schema / properties / limit / maximum
```
Added value: +50
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

addedInput schema / properties / query / minLength
```
Added value: +1
```
addedInput schema / properties / query / pattern
```
Added value: +"\\S"
```

8 tool updatesv0.0.4May 3, 2026

Changedai_search6 fields changed

changedInput schema / properties / limit / description

Previous value: -"Result limit"New value: +"Maximum number of results (default: 10)"

removedInput schema / properties / provider / anyOf

Removed value: -[
-  {
-    "const": "perplexity"
-  },
-  {
-    "const": "kagi_fastgpt"
-  },
-  {
-    "const": "exa_answer"
-  }
-]

changedInput schema / properties / provider / description

Previous value: -"AI provider"New value: +"AI search provider to use"

addedInput schema / properties / provider / enum
```
Added value: +[
+  "kagi_fastgpt"
+]
```
addedInput schema / properties / provider / type
```
Added value: +"string"
```

changedInput schema / properties / query / description

Previous value: -"Query"New value: +"Question or search query"

Removedfirecrawl_process
Removedjina_grounding_enhance
Removedkagi_enrichment_enhance
Removedkagi_summarizer_process
Removedtavily_extract_process
Addedweb_extract

Changedweb_search8 fields changed

changedInput schema / properties / exclude_domains / description

Previous value: -"Domains to exclude"New value: +"Exclude results from these domains"

changedInput schema / properties / include_domains / description

Previous value: -"Domains to include"New value: +"Only return results from these domains"

changedInput schema / properties / limit / description

Previous value: -"Result limit"New value: +"Maximum number of results (default: 10)"

removedInput schema / properties / provider / anyOf

Removed value: -[
-  {
-    "const": "tavily"
-  },
-  {
-    "const": "brave"
-  },
-  {
-    "const": "kagi"
-  },
-  {
-    "const": "exa"
-  }
-]

changedInput schema / properties / provider / description

Previous value: -"Search provider"New value: +"Search provider to use"

addedInput schema / properties / provider / enum

Added value: +[
+  "tavily",
+  "brave",
+  "kagi",
+  "kagi_enrichment"
+]

addedInput schema / properties / provider / type
```
Added value: +"string"
```

changedInput schema / properties / query / description

Previous value: -"Query"New value: +"Search query"

18 tool updatesv1.0.0Jan 3, 2026

Addedai_search
Removedbrave_search
Removedfirecrawl_actions_process
Removedfirecrawl_crawl_process
Removedfirecrawl_extract_process
Removedfirecrawl_map_process
Addedfirecrawl_process
Removedfirecrawl_scrape_process
Changedjina_grounding_enhance2 fields changed
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- changedInput schema / properties / content / description
```
Previous value: -"Content to enhance"New value: +"Content"
```
Removedjina_reader_process
Changedkagi_enrichment_enhance2 fields changed
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- changedInput schema / properties / content / description
```
Previous value: -"Content to enhance"New value: +"Content"
```
Removedkagi_fastgpt_search
Removedkagi_search

Changedkagi_summarizer_process9 fields changed

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / properties / extract_depth / anyOf

Added value: +[
+  {
+    "const": "basic"
+  },
+  {
+    "const": "advanced"
+  }
+]

removedInput schema / properties / extract_depth / default
```
Removed value: -"basic"
```

changedInput schema / properties / extract_depth / description

Previous value: -"The depth of the extraction process. \"advanced\" retrieves more data but costs more credits."New value: +"Extraction depth"

removedInput schema / properties / extract_depth / enum
```
Removed value: -[
-  "basic",
-  "advanced"
-]
```
removedInput schema / properties / extract_depth / type
```
Removed value: -"string"
```

addedInput schema / properties / url / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

addedInput schema / properties / url / description
```
Added value: +"URL(s)"
```

removedInput schema / properties / url / oneOf

Removed value: -[
-  {
-    "description": "Single URL to process",
-    "type": "string"
-  },
-  {
-    "description": "Multiple URLs to process",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-]

Removedperplexity_search

Changedtavily_extract_process9 fields changed

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / properties / extract_depth / anyOf

Added value: +[
+  {
+    "const": "basic"
+  },
+  {
+    "const": "advanced"
+  }
+]

removedInput schema / properties / extract_depth / default
```
Removed value: -"basic"
```

changedInput schema / properties / extract_depth / description

Previous value: -"The depth of the extraction process. \"advanced\" retrieves more data but costs more credits."New value: +"Extraction depth"

removedInput schema / properties / extract_depth / enum
```
Removed value: -[
-  "basic",
-  "advanced"
-]
```
removedInput schema / properties / extract_depth / type
```
Removed value: -"string"
```

addedInput schema / properties / url / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

addedInput schema / properties / url / description
```
Added value: +"URL(s)"
```

removedInput schema / properties / url / oneOf

Removed value: -[
-  {
-    "description": "Single URL to process",
-    "type": "string"
-  },
-  {
-    "description": "Multiple URLs to process",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-]

Removedtavily_search
Addedweb_search

15 tool updatesAug 15, 2025
- First observedbrave_search
- First observedfirecrawl_actions_process
- First observedfirecrawl_crawl_process
- First observedfirecrawl_extract_process
- First observedfirecrawl_map_process
- First observedfirecrawl_scrape_process
- First observedjina_grounding_enhance
- First observedjina_reader_process
- First observedkagi_enrichment_enhance
- First observedkagi_fastgpt_search
- First observedkagi_search
- First observedkagi_summarizer_process
- First observedperplexity_search
- First observedtavily_extract_process
- First observedtavily_search

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored 2026-08-26 20:35 across 3 tools

Disambiguation5/5

Each tool has a clearly distinct job: web_search returns raw search results, ai_search returns synthesized answers with citations, and web_extract processes specific URLs. There is no meaningful overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern combining a domain prefix with an action: web_search, ai_search, web_extract. The naming style is uniform and predictable.

Tool Count5/5

Three tools is well-scoped for an omnisearch server covering the core needs of searching, getting AI answers, and extracting web content. Each tool earns its place without redundancy.

Completeness5/5

The toolset covers the full search-to-insight workflow: finding sources, getting synthesized answers, and extracting or summarizing content from URLs. There are no obvious dead ends or missing core operations for the stated purpose.

Maintenance

ActivityActive

ResponsivenessResponsive

Resources

Need Help?

Reddit Discussion

Related Servers

Related MCP Connectors

hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
238
Jina Reader A
io.github.pipeworx-io
Jina AI Reader/Search MCP — turn any URL into clean LLM-ready markdown, plus web search.
Web Scraping Search
2
qsearch A
io.github.theYahia
Multi-engine search for AI agents. Trust scoring, local corpus, MCP-native. Self-hostable, BYOK.
Search RAG Systems
23
Firecrawl MCP Server A
io.github.firecrawl
MCP server for Firecrawl — web search, scraping, and biomedical/arXiv paper search.
Browser Automation Web Scraping Search
317,575

Related MCP Servers

OneSearch MCP Server
Browser Automation Web Scraping Search
yokingma
A
license
A
quality
C
maintenance
A Model Context Protocol server that enables web search, scraping, crawling, and content extraction through multiple engines including SearXNG, Firecrawl, and Tavily.
Updated 2 months ago (2026-07-31 01:37 UTC)
4
325 npm
144
MIT
MCP Search Server
youill0317
-
license
Not graded
quality
Not graded
maintenance
A unified Model Context Protocol server that integrates multiple search providers including Brave, Tavily, Exa, Semantic Scholar, and arXiv. It enables users to perform web, news, and image searches alongside academic research and citation analysis through a single interface.
Updated 7 months ago (2026-03-08 13:58 UTC)
-
web-search-plus-mcp
Search Browser Automation RAG Systems
robbyczgw-cla
A
license
B
quality
A
maintenance
A Model Context Protocol server that gives AI assistants access to 7 search providers with intelligent auto-routing. Analyzes query intent and picks the best provider automatically — no manual switching needed. Install, configure your keys, and go.
Updated 21 hours ago (2026-10-10 08:55 UTC)
2
1,253 PyPI
5
MIT
MCP Server Metasearch
Search Web Scraping Browser Automation
busigui2023
A
license
Not graded
quality
D
maintenance
A unified MCP server aggregating 15 web search and extraction tools across 5 providers (Jina, Tavily, Exa, Firecrawl, Bocha) with automatic API key validation and plugin architecture.
Updated 4 months ago (2026-06-07 17:28 UTC)
MIT

mcp-omnisearch

特征

🔍 搜索工具

🎯 搜索运算符

常见搜索功能

示例用法

提供商能力

🤖 AI 响应工具

📄内容处理工具

🔄 增强工具

灵活的 API 密钥要求

配置

克莱恩配置

带有 WSL 配置的 Claude 桌面

环境变量

API

搜索工具

搜索_塔维利

search_brave

搜索_kagi

AI响应工具

ai_perplexity

ai_kagi_fastgpt

内容处理工具

process_jina_reader

process_kagi_summarizer

process_tavily_extract

firecrawl_scrape_process

firecrawl_crawl_process

firecrawl_map_process

firecrawl_extract_process

firecrawl_actions_process

增强工具

增强_kagi_enrichment

增强_jina_grounding

发展

设置

出版

故障排除

API 密钥和访问权限

速率限制

贡献

执照

致谢

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches