openserpapi/mcp

Developer tools

このページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。原文を見る

3 stars 2 forks 品質 82 トレンド 24MIT

Repository Install

Model Context Protocol server for OpenSERP search engine API

概要

Live search on six engines (Google, Bing, Yandex, Baidu, DuckDuckGo, Ecosia), image search and single/batch page extraction for AI agents. Results keep the source engine and rank. Runs against a self-hosted OpenSERP server or OpenSERP Cloud. When OPENSERP_API_KEY is not set, the server uses OSS mode at http://localhost:7000 and writes: Set OPENSERP_API_KEY to use OpenSERP Cloud. API keys are available at https://openserp.org/dashboard/keys. Set OPENSERP_BASE_URL to target another compatible OpenSERP API base URL. extract and batch_extract cut long pages to fit an agent's context: 20,000 characters per page, or 40,000 shared across a batch (at least 2,000 per URL). Cut content ends with a [truncated: ...] line and is flagged (truncated / metadata.truncated). Pass maxChars to read more. - Search Google for current docs and return the top 5 URLs. - Compare Google and Bing results for an SEO keyword. - Extract clean Markdown from a URL before passing it to an LLM.

README

以下は原文 README の抜粋です。原文を見る。

@openserp/mcp

When OPENSERP_API_KEY is not set, the server uses OSS mode at http://localhost:7000 and writes:

[openserp-mcp] No OPENSERP_API_KEY set - using OSS mode at http://localhost:7000.
[openserp-mcp] Get an API key: https://openserp.org/dashboard/keys
[openserp-mcp] Docs: https://openserp.org/docs | Issues: https://github.com/openserpapi/mcp/issues

Set OPENSERP_API_KEY to use OpenSERP Cloud. API keys are available at https://openserp.org/dashboard/keys. Set OPENSERP_BASE_URL to target another compatible OpenSERP API base URL.

Install

npm install -g @openserp/mcp

You can also run it without installing:

npx -y @openserp/mcp --stdio

Tools

Tool	Use it when
`search`	The engine matters (Yandex for Russian, Baidu for Chinese), or you page with `start`
`any_search`	You want a preferred engine with fallbacks, in your order
`fast_search`	Any engine will do; picks the healthiest, fastest one
`mega_search`	You compare engines or want wider coverage; results keep engine and rank
`image_search`	Images from one engine
`mega_image`	Images merged from several engines
`extract`	Reading one page as Markdown
`batch_extract`	Reading several pages (up to 20) in one call; a failed URL doesn’t fail the batch
`list_engines`	Searches keep failing and you need a healthy engine
`get_usage`	Checking the Cloud credit balance or what the last call cost

extract and batch_extract cut long pages to fit an agent’s context: 20,000 characters per page, or 40,000 shared across a batch (at least 2,000 per URL). Cut content ends with a [truncated: ...] line and is flagged (truncated / metadata.truncated). Pass maxChars to read more.

Quick Examples

Ask your MCP client to:

Search Google for current docs and return the top 5 URLs.
Compare Google and Bing results for an SEO keyword.
Extract clean Markdown from a URL before passing it to an LLM.
Ground an answer in several sources at once with batch_extract - up to 20 URLs in one round-trip, where a dead link returns an error item instead of failing the batch.
Read a geo-fenced page as a local visitor by passing region: "DE".
Check remaining Cloud credits with get_usage.

Cloud search parameters

GitHub で README 全文を見る

インストール

npx -y @openserp/mcp

MCP 初心者？mcpskill.org のガイドから始めましょう →

設定

{
  "mcpServers": {
    "openserp": {
      "command": "npx",
      "args": ["-y", "@openserp/mcp"]
    }
  }
}