de en es ja ko ru zh

OneSearch MCP Server

Name: OneSearch MCP Server
Author: yokingma

by yokingma

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

🚀 OneSearch MCPサーバー: ウェブ検索 & クロール & スクレイパー & コンテンツ準備

ウェブ検索、ローカルブラウザ検索、および agent-browser を使用したスクレイピング機能のために、複数の検索プロバイダーと統合するModel Context Protocol (MCP) サーバーの実装です。

機能

ウェブサイトからのウェブ検索、スクレイピング、クロール、およびコンテンツの事前処理。
複数の検索エンジンとウェブスクレイパーをサポート: SearXNG、Tavily、DuckDuckGo、Bing、Google、Zhipu (智谱)、Exa、Bocha (博查) など。
ローカルウェブ検索 (ブラウザ検索)、複数の検索エンジンをサポート: Bing、Google、Baidu、Sogou など。
- ブラウザ自動化に agent-browser を使用。
- 無料、APIキー不要。
有効なツール: one_search, one_scrape, one_map, one_extract

Related MCP server: Firecrawl MCP Server

v1.1.0以前からの移行

v1.1.0での破壊的変更:

Firecrawlの削除: Firecrawl統合は削除されました。代わりに、外部APIサービスを必要とせずに同様の機能を提供する agent-browser が採用されました。
新しいブラウザ要件: Chromiumブラウザをインストールする必要があります（「前提条件」セクションを参照）。
環境変数: FIRECRAWL_API_URL および FIRECRAWL_API_KEY は使用されなくなりました。

変更点:

one_scrape および one_map は、Firecrawlの代わりに agent-browser を使用するようになりました。
one_extract は、組み込みのLLM抽出を実行する代わりに、ダウンストリーム分析のためにマルチURLページコンテンツを事前処理するようになりました。
すべてのブラウザベースの操作がローカルで処理されるようになり、プライバシーが向上し、APIコストもかかりません。

移行手順:

Chromiumブラウザをインストールする（「前提条件」を参照）
環境変数から FIRECRAWL_API_URL と FIRECRAWL_API_KEY を削除する
最新バージョンに更新する: npm install -g one-search-mcp@latest

前提条件

ブラウザ要件: このサーバーはウェブスクレイピングとローカル検索に agent-browser を使用しており、Chromiumベースのブラウザが必要です。

朗報: サーバーはシステムにインストール済みのブラウザを自動的に検出して使用します:

✅ Google Chrome
✅ Microsoft Edge
✅ Chromium
✅ Google Chrome Canary

これらのブラウザがインストールされていない場合は、以下を行ってください:

# Option 1: Install Google Chrome (Recommended)
# Download from: https://www.google.com/chrome/

# Option 2: Install Microsoft Edge
# Download from: https://www.microsoft.com/edge

# Option 3: Install Chromium via agent-browser
npx agent-browser install

# Option 4: Install Chromium directly
# Download from: https://www.chromium.org/getting-involved/download-chromium/

インストール

Claude Code CLIを使用する場合 (推奨)

# Add to Claude Code with default settings (local search)
claude mcp add one-search-mcp -- npx -y one-search-mcp

# Add with custom search provider (e.g., SearXNG)
claude mcp add one-search-mcp -e SEARCH_PROVIDER=searxng -e SEARCH_API_URL=http://127.0.0.1:8080 -- npx -y one-search-mcp

# Add with Tavily API
claude mcp add one-search-mcp -e SEARCH_PROVIDER=tavily -e SEARCH_API_KEY=your_api_key -- npx -y one-search-mcp

手動インストール

# Install globally (Optional)
npm install -g one-search-mcp

# Or run directly with npx
npx -y one-search-mcp

Dockerを使用する場合

Dockerイメージにはすべての依存関係（Chromiumブラウザ）がプリインストールされており、追加のセットアップは不要です。

イメージのプル:

# From GitHub Container Registry
docker pull ghcr.io/yokingma/one-search-mcp:latest

# Or from Docker Hub
docker pull zacma/one-search-mcp:latest

Claude Desktopでの設定:

{
  "mcpServers": {
    "one-search-mcp": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "ghcr.io/yokingma/one-search-mcp:latest"],
      "env": {
        "SEARCH_PROVIDER": "local"
      }
    }
  }
}

カスタム検索プロバイダーを使用する場合:

{
  "mcpServers": {
    "one-search-mcp": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "SEARCH_PROVIDER=tavily",
        "-e", "SEARCH_API_KEY=your_api_key",
        "ghcr.io/yokingma/one-search-mcp:latest"
      ]
    }
  }
}

環境変数

検索エンジン:

SEARCH_PROVIDER (オプション): 使用する検索プロバイダー。searxng, duckduckgo, bing, tavily, google, zhipu, exa, bocha, local をサポート。デフォルトは local です。
SEARCH_API_URL (オプション): SearxNG APIのURL、または google の場合はGoogleカスタム検索エンジンID。
SEARCH_API_KEY (オプション): 検索プロバイダーのAPIキー。tavily, bing, google, zhipu, exa, bocha で必要です。

// supported search providers
export type SearchProvider = 'searxng' | 'duckduckgo' | 'bing' | 'tavily' | 'google' | 'zhipu' | 'exa' | 'bocha' | 'local';

検索プロバイダーの設定

プロバイダー	APIキーが必要	API URLが必要	備考
`local`	いいえ	いいえ	無料、ブラウザ自動化を使用
`duckduckgo`	いいえ	いいえ	無料、APIキー不要
`searxng`	オプション	はい	セルフホスト型メタ検索エンジン
`bing`	はい	いいえ	Bing Search API
`tavily`	はい	いいえ	Tavily API
`google`	はい	はい (検索エンジンID)	Google Custom Search
`zhipu`	はい	いいえ	智谱 AI
`exa`	はい	いいえ	Exa AI
`bocha`	はい	いいえ	博查 AI

その他のMCPクライアントの設定

Claude Desktop

Claude Desktopの設定ファイルに追加してください:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "one-search-mcp": {
      "command": "npx",
      "args": ["-y", "one-search-mcp"],
      "env": {
        "SEARCH_PROVIDER": "local"
      }
    }
  }
}

Cursor

mcp.json ファイルに追加してください:

{
  "mcpServers": {
    "one-search-mcp": {
      "command": "npx",
      "args": ["-y", "one-search-mcp"],
      "env": {
        "SEARCH_PROVIDER": "local"
      }
    }
  }
}

Windsurf

./codeium/windsurf/model_config.json ファイルに追加してください:

{
  "mcpServers": {
    "one-search-mcp": {
      "command": "npx",
      "args": ["-y", "one-search-mcp"],
      "env": {
        "SEARCH_PROVIDER": "local"
      }
    }
  }
}

SearXNGのセルフホスト (オプション)

SearXNGを検索プロバイダーとして使用したい場合は、Dockerを使用してローカルにデプロイできます:

前提条件:

Dockerがインストールされ、実行されていること (バージョン20.10.0以上)
少なくとも4GBのRAMが利用可能であること

クイックスタート:

# Clone SearXNG Docker repository
git clone https://github.com/searxng/searxng-docker.git
cd searxng-docker

# Start SearXNG
docker compose up -d

デプロイ後、SearXNGはデフォルトで http://127.0.0.1:8080 で利用可能になります。

OneSearchでSearXNGを使用するように設定:

# Set environment variables
export SEARCH_PROVIDER=searxng
export SEARCH_API_URL=http://127.0.0.1:8080

詳細については、公式SearXNG Dockerドキュメントを参照してください。

トラブルシューティング

「Browser not found」エラー

「Browser not found」のようなエラーが表示される場合、サーバーはインストールされているChromiumベースのブラウザを検出できませんでした。以下のいずれかをインストールしてください:

Google Chrome: https://www.google.com/chrome/
Microsoft Edge: https://www.microsoft.com/edge
Chromium: https://www.chromium.org/getting-involved/download-chromium/

または、agent-browser経由でインストールしてください:

npx agent-browser install

ライセンス

MITライセンス - 詳細は LICENSE ファイルを参照してください。

Available Tools

4 tools

one_extractA

Fetch and preprocess page content from one or more URLs. Returns cleaned text blocks that can be passed to downstream tools or models.

ParametersJSON Schema

Name	Required	Description	Default
`urls`	Yes	List of URLs to extract information from

TDQS

A3.5/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. 'Returns cleaned text blocks' hints at preprocessing but does not detail cleaning steps, error handling, or auth needs.

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 concise sentences, front-loaded with action, then output. No wasted words.

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?

For a simple tool (1 param, no output schema), description adequately covers purpose and output. Lacks details on cleaning specifics, error handling, or limits.

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

Parameters4/5

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

Schema covers parameter with 100% coverage. Description adds value by specifying preprocessing and output type ('cleaned text blocks'), going beyond schema's 'extract information'.

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

Purpose5/5

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

Description clearly states the verb 'fetch and preprocess' and the resource 'page content from URLs'. Differentiates from siblings: one_map, one_scrape, one_search.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance. Mentions downstream use but lacks context for choosing over siblings.

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

one_mapA

Discover URLs from a starting point by loading a page in the browser and extracting links from its HTML.

ParametersJSON Schema

Name	Required	Description
`url`	Yes	Starting URL for URL discovery
`limit`	No	Maximum number of URLs to return
`search`	No	Optional search term to filter URLs
`includeSubdomains`	No	Include URLs from subdomains in results

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose the core mechanism—loading a page in the browser and extracting links from its HTML—but it omits important details such as whether the crawl is recursive, whether subdomains are included by default, or any performance/rate implications.

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?

The description is a single, front-loaded sentence that immediately conveys the main action and mechanism. It contains no filler, repetition, or unnecessary detail.

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?

The description is minimal but sufficient for a simple one-page link extractor. However, with no output schema, it leaves ambiguity about return format and whether discovery is recursive or limited to the initial page, which is important for a mapping tool with four parameters.

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 coverage is 100%, so the description does not need to add much parameter detail. It simply reinforces 'starting point' for the url parameter and adds no new meaning beyond what the schema already provides.

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

Purpose5/5

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

The description states a specific action: discover URLs from a starting point by loading a page in the browser and extracting HTML links. This clearly distinguishes it from sibling tools like one_extract, one_search, and one_scrape, which focus on other tasks.

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 clear context that this tool is for mapping/discovering URLs from a starting page, which implies when it should be selected. However, it does not explicitly mention alternatives or state when not to use it, so it falls 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.

one_scrapeA

Scrape a single webpage and return markdown, HTML, links, or a screenshot. Supports navigation timeout, TLS verification control, full-page screenshots, bounded pre-scrape actions, and advanced executeJavascript only when allowExecuteJavascript is true.

ParametersJSON Schema

Name	Required	Description
`url`	Yes	The URL to scrape
`actions`	No	List of pre-scrape actions to run before content capture. Standard actions are bounded; executeJavascript requires allowExecuteJavascript: true.
`formats`	No	Content formats to extract (default: ['markdown'])
`timeout`	No	Maximum time in milliseconds to wait for the page to load
`waitFor`	No	Time in milliseconds to wait for dynamic content to load
`skipTlsVerification`	No	Skip TLS certificate verification
`allowExecuteJavascript`	No	Must be true when actions contain executeJavascript. Use only for advanced page-side scripting.

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It notably discloses support for navigation timeout, TLS verification control, full-page screenshots, bounded pre-scrape actions, and the gating of executeJavascript. It does not mention error behavior or return structure, but these are less critical for a scraping tool.

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?

The description is concise at two sentences, front-loaded with the core purpose, and every clause adds value (outputs, timeout, TLS, screenshots, actions). There is no fluff or redundancy.

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?

Given the tool's complexity (7 parameters, no output schema, no annotations), the description provides a good overview of capabilities but lacks details on return value structure, error handling, or pagination/navigation behavior. It is adequate but has clear gaps, especially regarding what the returned data looks like for each format.

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?

Since schema description coverage is 100%, the baseline is 3. The description adds some context by mentioning 'bounded pre-scrape actions' and the executeJavascript requirement, which aligns with the actions and allowExecuteJavascript parameters. However, it does not add significant syntax or format details beyond what the schema already provides.

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

Purpose4/5

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

The description clearly identifies the tool's action ('Scrape a single webpage') and its outputs ('markdown, HTML, links, or a screenshot'), which distinguishes it from the sibling tools by focusing on single-page scraping. It is a specific verb+resource statement, though it does not explicitly contrast with siblings like 'one_extract'.

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?

The description implies usage for scraping a single webpage and mentions the prerequisite for executeJavascript ('only when allowExecuteJavascript is true'). However, it does not explicitly state when to choose this tool over alternatives such as one_extract, one_search, or one_map, nor does it provide exclusion criteria.

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

one_searchB

Search and retrieve content from web pages. Returns SERP results by default (url, title, description).

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return (default: 10)
`query`	Yes	Search query string
`language`	No	Language code for search results (default: auto)
`timeRange`	No	Time range for search results (default: all)
`categories`	No	Categories to search for (default: general)

TDQS

B3.2/5.0

Behavior3/5

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

The description states it returns SERP results (url, title, description), which is helpful. However, with no annotations, it lacks details on pagination, rate limits, or blocking behaviors. It adequately covers the basic return value but could be more transparent.

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?

The description is extremely concise with two sentences, front-loading the purpose. Every sentence adds value with no redundancy or filler.

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?

Given the absence of an output schema and the presence of 5 parameters (including enums for categories and timeRange), the description does not fully explain the usage of these parameters or the structure of the response beyond basic SERP fields. It feels incomplete for an agent to use effectively.

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?

Input schema coverage is 100%, so the schema already describes all parameters. The description adds no extra meaning beyond what the schema provides.

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

Purpose4/5

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

The description clearly states the tool searches and retrieves content from web pages and returns SERP results with URL, title, and description. It is specific but does not explicitly distinguish itself from sibling tools like one_map or one_scrape.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. No when-not-to-use or prerequisite information is given.

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.

2 tool updatesv1.2.4Jul 31, 2026

Changedone_map2 fields changed

removedInput schema / properties / ignoreSitemap

Removed value: -{
-  "description": "Skip sitemap.xml discovery and only use HTML links",
-  "type": "boolean"
-}

removedInput schema / properties / sitemapOnly

Removed value: -{
-  "description": "Only use sitemap.xml for discovery, ignore HTML links",
-  "type": "boolean"
-}

Changedone_scrape11 fields changed

changedInput schema / properties / actions / description

Previous value: -"List of actions to perform before scraping"New value: +"List of pre-scrape actions to run before content capture. Standard actions are bounded; executeJavascript requires allowExecuteJavascript: true."

changedInput schema / properties / actions / items / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "milliseconds": {
-        "description": "Time to wait in milliseconds",
-        "type": "number"
-      },
-      "type": {
-        "const": "wait",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "milliseconds"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "selector": {
-        "description": "CSS selector for the target element",
-        "type": "string"
-      },
-      "type": {
-        "const": "click",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "selector"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "fullPage": {
-        "description": "Take full page screenshot",
-        "type": "boolean"
-      },
-      "type": {
-        "const": "screenshot",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "selector": {
-        "description": "CSS selector for the target element",
-        "type": "string"
-      },
-      "text": {
-        "description": "Text to write",
-        "type": "string"
-      },
-      "type": {
-        "const": "write",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "selector",
-      "text"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "key": {
-        "description": "Key to press",
-        "type": "string"
-      },
-      "type": {
-        "const": "press",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "key"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "direction": {
-        "description": "Scroll direction",
-        "enum": [
-          "up",
-          "down"
-        ],
-        "type": "string"
-      },
-      "type": {
-        "const": "scroll",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "direction"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "type": {
-        "const": "scrape",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "script": {
-        "description": "JavaScript code to execute",
-        "type": "string"
-      },
-      "type": {
-        "const": "executeJavascript",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "script"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "milliseconds": {
+        "description": "Time to wait in milliseconds",
+        "type": "number"
+      },
+      "type": {
+        "const": "wait",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "milliseconds"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "selector": {
+        "description": "CSS selector for the target element",
+        "type": "string"
+      },
+      "type": {
+        "const": "click",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "selector"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "selector": {
+        "description": "CSS selector for the target element",
+        "type": "string"
+      },
+      "text": {
+        "description": "Text to write",
+        "type": "string"
+      },
+      "type": {
+        "const": "write",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "selector",
+      "text"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "key": {
+        "description": "Key to press",
+        "type": "string"
+      },
+      "type": {
+        "const": "press",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "key"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "direction": {
+        "description": "Scroll direction",
+        "enum": [
+          "up",
+          "down"
+        ],
+        "type": "string"
+      },
+      "type": {
+        "const": "scroll",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "direction"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "script": {
+        "description": "JavaScript code to execute",
+        "type": "string"
+      },
+      "type": {
+        "const": "executeJavascript",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "script"
+    ],
+    "type": "object"
+  }
+]

addedInput schema / properties / allowExecuteJavascript

Added value: +{
+  "description": "Must be true when actions contain executeJavascript. Use only for advanced page-side scripting.",
+  "type": "boolean"
+}

removedInput schema / properties / excludeTags

Removed value: -{
-  "description": "HTML tags to exclude from extraction",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / extract

Removed value: -{
-  "additionalProperties": false,
-  "description": "Configuration for structured data extraction",
-  "properties": {
-    "prompt": {
-      "description": "User prompt for LLM extraction",
-      "type": "string"
-    },
-    "schema": {
-      "additionalProperties": {},
-      "description": "Schema for structured data extraction",
-      "type": "object"
-    },
-    "systemPrompt": {
-      "description": "System prompt for LLM extraction",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}

changedInput schema / properties / formats / items / enum

Previous value: -[
-  "markdown",
-  "html",
-  "rawHtml",
-  "screenshot",
-  "links",
-  "screenshot@fullPage",
-  "extract"
-]New value: +[
+  "markdown",
+  "html",
+  "rawHtml",
+  "screenshot",
+  "links",
+  "screenshot@fullPage"
+]

removedInput schema / properties / includeTags

Removed value: -{
-  "description": "HTML tags to specifically include in extraction",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / location

Removed value: -{
-  "additionalProperties": false,
-  "description": "Location settings for scraping",
-  "properties": {
-    "country": {
-      "description": "Country code for geolocation",
-      "type": "string"
-    },
-    "languages": {
-      "description": "Language codes for content",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    }
-  },
-  "type": "object"
-}

removedInput schema / properties / mobile

Removed value: -{
-  "description": "Use mobile viewport",
-  "type": "boolean"
-}

removedInput schema / properties / onlyMainContent

Removed value: -{
-  "description": "Extract only the main content, filtering out navigation, footers, etc.",
-  "type": "boolean"
-}

removedInput schema / properties / removeBase64Images

Removed value: -{
-  "description": "Remove base64 encoded images from output",
-  "type": "boolean"
-}

4 tool updatesv1.2.1May 6, 2026

Changedone_extract8 fields changed

addedInput schema / $schema

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

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / allowExternalLinks

Removed value: -{
-  "description": "Allow extraction from external links",
-  "type": "boolean"
-}

removedInput schema / properties / enableWebSearch

Removed value: -{
-  "description": "Enable web search for additional context",
-  "type": "boolean"
-}

removedInput schema / properties / includeSubdomains

Removed value: -{
-  "description": "Include subdomains in extraction",
-  "type": "boolean"
-}

removedInput schema / properties / prompt

Removed value: -{
-  "description": "Prompt for the LLM extraction",
-  "type": "string"
-}

removedInput schema / properties / schema

Removed value: -{
-  "description": "JSON schema for structured data extraction",
-  "type": "object"
-}

removedInput schema / properties / systemPrompt

Removed value: -{
-  "description": "System prompt for LLM extraction",
-  "type": "string"
-}

Changedone_map2 fields changed
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / additionalProperties
```
Added value: +false
```

Changedone_scrape9 fields changed

addedInput schema / $schema

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

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / actions / items / anyOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "milliseconds": {
+        "description": "Time to wait in milliseconds",
+        "type": "number"
+      },
+      "type": {
+        "const": "wait",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "milliseconds"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "selector": {
+        "description": "CSS selector for the target element",
+        "type": "string"
+      },
+      "type": {
+        "const": "click",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "selector"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "fullPage": {
+        "description": "Take full page screenshot",
+        "type": "boolean"
+      },
+      "type": {
+        "const": "screenshot",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "selector": {
+        "description": "CSS selector for the target element",
+        "type": "string"
+      },
+      "text": {
+        "description": "Text to write",
+        "type": "string"
+      },
+      "type": {
+        "const": "write",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "selector",
+      "text"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "key": {
+        "description": "Key to press",
+        "type": "string"
+      },
+      "type": {
+        "const": "press",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "key"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "direction": {
+        "description": "Scroll direction",
+        "enum": [
+          "up",
+          "down"
+        ],
+        "type": "string"
+      },
+      "type": {
+        "const": "scroll",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "direction"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "type": {
+        "const": "scrape",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "script": {
+        "description": "JavaScript code to execute",
+        "type": "string"
+      },
+      "type": {
+        "const": "executeJavascript",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "script"
+    ],
+    "type": "object"
+  }
+]

removedInput schema / properties / actions / items / properties

Removed value: -{
-  "direction": {
-    "description": "Scroll direction",
-    "enum": [
-      "up",
-      "down"
-    ],
-    "type": "string"
-  },
-  "fullPage": {
-    "description": "Take full page screenshot",
-    "type": "boolean"
-  },
-  "key": {
-    "description": "Key to press (for press action)",
-    "type": "string"
-  },
-  "milliseconds": {
-    "description": "Time to wait in milliseconds (for wait action)",
-    "type": "number"
-  },
-  "script": {
-    "description": "JavaScript code to execute",
-    "type": "string"
-  },
-  "selector": {
-    "description": "CSS selector for the target element",
-    "type": "string"
-  },
-  "text": {
-    "description": "Text to write (for write action)",
-    "type": "string"
-  },
-  "type": {
-    "description": "Type of action to perform",
-    "enum": [
-      "wait",
-      "click",
-      "screenshot",
-      "write",
-      "press",
-      "scroll",
-      "scrape",
-      "executeJavascript"
-    ],
-    "type": "string"
-  }
-}

removedInput schema / properties / actions / items / required
```
Removed value: -[
-  "type"
-]
```
removedInput schema / properties / actions / items / type
```
Removed value: -"object"
```
addedInput schema / properties / extract / additionalProperties
```
Added value: +false
```
addedInput schema / properties / extract / properties / schema / additionalProperties
```
Added value: +{}
```
addedInput schema / properties / location / additionalProperties
```
Added value: +false
```

Changedone_search2 fields changed
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / additionalProperties
```
Added value: +false
```

4 tool updatesAug 15, 2025
- First observedone_extract
- First observedone_map
- First observedone_scrape
- First observedone_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.7/5.0

Scored 2026-07-31 22:35 across 4 tools

Disambiguation4/5

Each tool has a distinct core function: search returns SERP results, extract preprocesses multiple URLs, scrape handles single-page advanced operations, and map discovers links. There is minor overlap between extract and scrape for fetching page content, but their descriptions make the intended use cases clear.

Naming Consistency5/5

All tool names follow the consistent pattern 'one_' prefix followed by a lowercase action verb (search, extract, scrape, map), with underscores between words. No mixed conventions or camelCase.

Tool Count5/5

Four tools is well within the ideal range for a focused search/scraping server. Each tool covers a distinct aspect of web research, making the set feel appropriately scoped without being bloated.

Completeness4/5

The tool set covers the primary workflows: searching, extracting content, single-page scraping with advanced options, and link discovery. Minor gaps exist, such as no dedicated batch scraping tool, but the combined functionality handles most common use cases.

Maintenance

ActivitySlowing

ResponsivenessWithin a week

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
SSearch B
cc.ssearch
Free web search for AI agents. No API key required. Hosted MCP in active development.
Search Browser Automation
71
MESSORA A
dev.messora
Scrape, crawl and search the web for AI agents via MCP.
Web Scraping Browser Automation Search
51
Keenable Web Search A
ai.keenable.api
Docs: https://docs.keenable.ai/mcp-server Keenable is a free, remote MCP server that gives agents access to the web index. Search the web with ranked results and date/site filters, then fetch any indexed page as clean markdown. Works out of the box with no account or API key.
Research & Data Search Web Scraping
23

Related MCP Servers

WebSearch
Web Scraping Browser Automation Search
josemartinrodriguezmortaloni
F
license
C
quality
C
maintenance
Built as a Model Context Protocol (MCP) server that provides advanced web search, content extraction, web crawling, and scraping capabilities using the Firecrawl API.
Updated 3 months ago (2026-06-17 03:44 UTC)
4
1
-
Firecrawl MCP Server
Web Scraping RAG Systems Browser Automation
mcma123
A
license
B
quality
D
maintenance
A Model Context Protocol server that enables AI assistants to perform advanced web scraping, crawling, searching, and data extraction through the Firecrawl API.
Updated 2 years ago (2025-03-10 04:55 UTC)
9
185,102 npm
MIT
MCP Web Search Tool
Search Web Scraping Browser Automation
gabrimatic
A
license
A
quality
C
maintenance
A Model Context Protocol server that provides real-time web search capabilities to AI assistants through pluggable search providers, currently integrated with the Brave Search API.
Updated 18 days ago (2026-09-10 00:00 UTC)
5
16
MIT
Firecrawl MCP Server
ampcome-mcps
A
license
A
quality
D
maintenance
A Model Context Protocol server that enables web scraping, crawling, and content extraction capabilities through integration with Firecrawl.
Updated a year ago (2025-07-15 05:56 UTC)
8
185,102 npm
2
MIT

🚀 OneSearch MCPサーバー: ウェブ検索 & クロール & スクレイパー & コンテンツ準備

機能

v1.1.0以前からの移行

前提条件

インストール

Claude Code CLIを使用する場合 (推奨)

手動インストール

Dockerを使用する場合

環境変数

検索プロバイダーの設定

その他のMCPクライアントの設定

Claude Desktop

Cursor

Windsurf

SearXNGのセルフホスト (オプション)

トラブルシューティング

「Browser not found」エラー

ライセンス

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches