mcp-retriever

io.github.keiranhaaxv0.0.24更新於 Oct 8, 2026

One MCP server for web search, page extraction, and cited research.

已驗證STDIO僅桌面Web Search & ScrapingKnowledge & Memory

概覽

AI 產生的概覽

讓助理跨多個供應商進行網路搜尋、擷取與爬取網頁，並回傳附引用的研究結果。

功能
透過 web_search_fused 將兩三個搜尋供應商的結果合併成去重後的排名，並在某個供應商失敗時回傳各供應商狀態。可擷取頁面內容、爬取網站，並在啟用封存回退時從 Wayback Machine 快照還原 404 或 410 頁面。可選的支出上限、冷卻時間與大型結果分頁存取有助於控制用量。
適用情境
當助理需要附引用的網路搜尋與網頁閱讀，或想同時查詢多個搜尋供應商並合併排名時使用。適合研究檢索類工作流程，尤其是希望供應商金鑰不寫入用戶端設定的情境。
執行需求
透過 stdio 在本機執行，需要 Node.js 22 或更新版本。至少需要一個供應商金鑰（Tavily、Brave、Exa、You.com、GitHub、Linkup、Firecrawl 或 Context.dev），或自建 SearXNG 執行個體。金鑰存放在憑證檔案而非用戶端設定；設定後需重新啟動用戶端。
安裝前請注意
供應商金鑰存放在本機憑證檔案中，計費金鑰檢查需要使用者同意。支出上限依賴供應商回報的用量而非估算成本，因此未必能限制實際支出。每個伺服器執行個體共用同一個信任邊界，其結果儲存不應供互不信任的用戶端使用。搜尋與頁面擷取會把查詢和網址傳送給第三方供應商。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 mcp-retriever，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

mcp-retriever

One MCP server for web search, page extraction, and cited research. Use your own providers, combine their results, and keep API keys out of client configs.

  • Search together: query two or three providers, deduplicate URLs, and merge rankings with web_search_fused.
  • Read more: extract pages, crawl sites, and recover 404/410 pages from Wayback Machine snapshots when archive fallback is enabled.
  • Control usage: optional spending caps for provider-reported usage, cooldowns, and paged access to large results.

Supports Tavily, Brave, Exa, You.com, SearXNG, GitHub, Linkup, Firecrawl, and Context.dev. Configure only what you use.

Quickstart

Requires Node.js 22+ and a provider key, or your own SearXNG instance.

bash
npx -y mcp-retriever setup

Choose providers, save keys privately, and connect your MCP client. The wizard writes Claude Desktop and Cursor entries, or shows the command/configuration for Claude Code and Codex. Billable key checks require consent.

[Setup wizard and provider selection]

Keys are stored in ~/.config/mcp-retriever/credentials.env, not in client configs. Restart your client after setup.

Client connection and key management

[Connecting MCP clients]

Add, test, or remove keys:

bash
npx mcp-retriever keys

[Key management menu]

Screenshots show a demo session with fixture credentials and a mocked key-check response, not a live provider validation.

Example

Call web_search_fused with two configured search providers:

json
{	"query": "reciprocal rank fusion hybrid search",	"providers": ["brave", "exa"],	"limit": 3}

Results include source providers and merged rankings. If a provider fails, available results are returned with per-provider status.

Documentation

Each server instance shares one trust boundary. Do not use its result store for mutually untrusted clients. Spending caps depend on provider-reported usage, not estimated costs.

License and origins

MIT. Formerly named mcp-omnisearch; a maintained fork of Scott Spence's mcp-omnisearch. When upgrading this fork, rename OMNISEARCH_* settings to RETRIEVER_*, omnisearch:// resources to retriever://, and _meta.omnisearch to _meta.retriever. Preserve the old result store and spending ledger when moving to ~/.cache/mcp-retriever/results; Docker/MCPO clients must also change /omnisearch to /retriever.

來源：README.md，提交 e0fd4d6

工具

0
工具後設資料尚未被收錄。

版本歷史

1
  1. v0.0.24最新Oct 8, 2026