G-Search MCP
G-Search MCP
複数のキーワードを同時に並行検索できる、Google 検索用の強力な MCP サーバーです。
このプロジェクトはgoogle-searchから変更されています。
利点
並列検索: Googleで複数のキーワードを同時に検索し、検索効率を向上します。
ブラウザの最適化: 効率的な並列検索のために、単一のブラウザインスタンスで複数のタブを開きます。
自動検証処理: CAPTCHA をインテリジェントに検出し、必要に応じてユーザー検証用の可視ブラウザ モードを有効にします。
ユーザー行動シミュレーション: 実際のユーザーの閲覧パターンをシミュレートして、検索エンジンによる検出の可能性を低減します。
構造化データ: 構造化された検索結果をJSON形式で返し、簡単に処理および分析できます。
設定可能なパラメータ: 検索結果の制限、タイムアウト設定、ロケール設定など、さまざまなパラメータ設定をサポートします。
Related MCP server: Enhanced Google Search MCP
クイックスタート
npx で直接実行します:
npx -y g-search-mcp初回セットアップ - ターミナルで次のコマンドを実行して、必要なブラウザをインストールします。
npx playwright install chromiumデバッグモード
--debugオプションを使用してデバッグ モードで実行します (ブラウザー ウィンドウを表示します)。
npx -y g-search-mcp --debugMCP を構成する
Claude Desktop でこの MCP サーバーを構成します。
MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"g-search": {
"command": "npx",
"args": ["-y", "g-search-mcp"]
}
}
}特徴
search- 複数のキーワードでGoogle検索を実行し、結果を返しますPlaywrightブラウザを使用して検索を実行します
次のパラメータをサポートします:
queries: 実行する検索クエリの配列(必須パラメータ)limit: クエリごとに返される結果の最大数。デフォルトは 10 です。timeout: ページ読み込みのタイムアウト(ミリ秒)。デフォルトは 60000(60 秒)noSaveState: ブラウザの状態を保存しないかどうか。デフォルトは falselocale: 検索結果のロケール設定。デフォルトは en-USdebug: デバッグモードを有効にするかどうか(ブラウザウィンドウを表示)、コマンドラインの --debug フラグを上書きします
使用例:
Use the search tool to search for "machine learning" and "artificial intelligence" on Google応答例:
{
"searches": [
{
"query": "machine learning",
"results": [
{
"title": "What is Machine Learning? | IBM",
"link": "https://www.ibm.com/topics/machine-learning",
"snippet": "Machine learning is a branch of artificial intelligence (AI) and computer science which focuses on the use of data and algorithms to imitate the way that humans learn, gradually improving its accuracy."
},
...
]
},
{
"query": "artificial intelligence",
"results": [
{
"title": "What is Artificial Intelligence (AI)? | IBM",
"link": "https://www.ibm.com/topics/artificial-intelligence",
"snippet": "Artificial intelligence leverages computers and machines to mimic the problem-solving and decision-making capabilities of the human mind."
},
...
]
}
]
}使用上のヒント
特殊なウェブサイトシナリオの取り扱い
検索パラメータの調整
検索結果数: さらに検索結果を表示するには:
Please return the top 20 search results for each keywordこれにより
limit: 20パラメータが設定されます。タイムアウト期間を増やす: 読み込みが遅い場合:
Please set the page loading timeout to 120 secondsこれにより、
timeoutパラメータが 120000 ミリ秒に調整されます。
ロケール設定の調整
検索地域の変更: 別のロケール設定を指定します:
Please use Chinese locale (zh-CN) for searchingこれにより
locale: "zh-CN"パラメータが設定されます。
デバッグとトラブルシューティング
デバッグモードを有効にする
動的デバッグのアクティブ化: 特定の検索操作中にブラウザ ウィンドウを表示するには:
Please enable debug mode for this search operationこれにより、サーバーが
--debugフラグなしで起動された場合でもdebug: trueが設定されます。
インストール
前提条件
Node.js 18以上
NPM または Yarn
ソースからインストール
リポジトリをクローンします。
git clone https://github.com/jae-jae/g-search-mcp.git
cd g-search-mcp依存関係をインストールします:
npm installPlaywright ブラウザをインストールします:
npm run install-browserサーバーを構築します。
npm run build発達
自動リビルド(開発モード)
npm run watchデバッグにMCP Inspectorを使用する
npm run inspector関連プロジェクト
fetcher-mcp : Playwrightヘッドレスブラウザを使用してWebページコンテンツを取得するための強力なMCPサーバー。インテリジェントなコンテンツ抽出、並列処理、リソース最適化などの機能を備えており、Webコンテンツのスクレイピングに最適なツールです。
ライセンス
MITライセンスに基づいてライセンスされています
Available Tools
1 toolsearchC
Search on Google for multiple keywords and return the results
| Name | Required | Description | Default |
|---|---|---|---|
| debug | No | Whether to enable debug mode (showing browser window), overrides the --debug command line flag if specified | |
| limit | No | Maximum number of results to return per query (default: 10) | |
| locale | No | Locale setting for search results (default: en-US) | |
| noSaveState | No | Whether to avoid saving browser state (default: false) | |
| queries | Yes | Array of search queries to perform | |
| timeout | No | Page loading timeout in milliseconds (default: 60000) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the action (search Google) and output (return results) but omits critical behavioral details like rate limits, authentication requirements, error handling, or what format results are returned in. This leaves significant gaps for an AI agent to understand tool behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise - a single sentence that efficiently communicates the core functionality. Every word earns its place with no redundant information. The structure is front-loaded with the essential action and purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with 6 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what format results are returned in, how errors are handled, or provide context about the search operation's limitations. The agent would need to guess about important behavioral aspects.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, providing comprehensive parameter documentation. The description adds minimal value beyond the schema, only implying that 'queries' parameter contains search keywords. No additional semantic context is provided about parameter interactions or usage patterns.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Search on Google for multiple keywords and return the results.' It specifies the verb (search), resource (Google), and scope (multiple keywords). However, with no sibling tools mentioned, there's no opportunity to differentiate from alternatives, preventing a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, constraints, or typical use cases. While there are no sibling tools to contrast with, the description lacks any contextual usage information.
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.
1 tool update
v1.0.0- First observed
search
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools, making disambiguation perfect. The single tool has a clear and distinct purpose without any ambiguity.
With only one tool, naming consistency is inherently perfect as there are no other tools to compare against. The tool name 'search' follows a simple verb pattern, which is appropriate for its function.
A single tool is too few for a search server, as it lacks basic operations like refining searches, handling different result types, or managing search history. This minimal set feels thin and incomplete for the apparent scope of a search service.
The tool set is severely incomplete for a search domain, offering only a basic search function without any support for advanced features like filtering, pagination, or accessing specific result details. This will likely cause agent failures when more complex search tasks are required.
Maintenance
Related MCP Connectors
MCP server for Google search results via SERP API
MCP server for 500+ pay-per-call web scraping, search, social, business, and financial data tools.
Official SerpApi MCP server for Google, Bing, and other search engines.
All HasData scraping tools in one MCP server: Google, TikTok, Instagram, maps, e-commerce and more.
Related MCP Servers
- AlicenseAqualityCmaintenanceAn MCP server that provides Google Search functionality with automatic API key rotation and intelligent quota management, enabling natural language search queries with advanced filtering options.111 npm1MIT
- AlicenseAqualityDmaintenanceA powerful Model Context Protocol (MCP) server that provides enhanced Google search capabilities with advanced anonymization and anti-detection features.14MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides web search and content fetching using real Chrome browsers via CDP, bypassing bot detection and requiring no API keys.20MIT
- FlicenseAqualityDmaintenanceMCP server that provides automated Google search capabilities, allowing query execution, result limiting, and optional related keywords retrieval.1-
Appeared in Searches
- A powerful MCP server for web search and information gathering
- Techniques for Scraping Dynamic Websites with JavaScript and Handling CAPTCHA or Proxy Issues
- Information about Meta ads or advertising on Meta platforms
- A list of all Minecraft plugins that can use SSE
- Information about DeepSearch or related platforms/tools