Google AI Mode MCP Server

Overview Schema Source Related Servers Discussions Admin

search_ai

Search Google AI Mode to get AI-generated summaries with citations, handling CAPTCHA detection and returning markdown results.

Instructions

Search Google AI Mode (udm=50) and return AI-generated summary with citations.

Returns markdown-formatted AI response with inline citations [1][2] and source list.

Features:

Automatic CAPTCHA detection and handling
Source extraction with citations
Clean markdown formatting
Stealth mode for anti-detection
Optional file saving with timestamp and sanitized filename

Note: If CAPTCHA is detected, you will be prompted to solve it in a visible browser window.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_ai"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	The search query to send to Google AI Mode
`filename`	No	Optional: Custom filename for saved result (only used if save_to_file is true). If not provided, auto-generates from query and timestamp.
`headless`	No	Optional: Run browser in headless mode (default: true). Set to false to see the browser.
`timeout_ms`	No	Optional: Timeout in milliseconds for the search (default: 120000 = 2 minutes)
`save_to_file`	No	Optional: Save markdown result to file (default: false). Saves to results/ folder with timestamp.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Aug 1, 2026

TDQS

A4.4/5.0

Behavior4/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 discloses CAPTCHA detection and handling, the visible browser prompt for CAPTCHA solving, stealth mode, and optional file saving. It doesn't cover rate limits or persistence, but the key behavioral traits are well communicated.

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 appropriately sized and front-loaded with the core purpose. Bullet points efficiently list features, and the note about CAPTCHA is well-placed. Every sentence adds value without redundancy.

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

Completeness4/5

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

Given no output schema, the description explains the return format (markdown with citations and source list). It covers the main behavioral aspects needed for an agent to invoke the tool safely. Some details like error handling or exact source list structure are omitted, but the description is sufficient for a tool of this complexity.

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?

The schema already covers 100% of parameters, so baseline is 3. The description adds value by explaining file saving behavior (timestamp and sanitized filename) and the CAPTCHA prompt interaction with headless mode, enhancing understanding beyond the raw schema descriptions.

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 clearly states the tool searches Google AI Mode (udm=50) and returns an AI-generated summary with citations. It specifies the exact resource and action, making it distinct and unambiguous. Even without sibling tools, the verb and resource are specific and complete.

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 provides clear context on what the tool does and when it would be appropriate (searching Google AI Mode). It doesn't explicitly mention when not to use it or alternatives, but the lack of siblings and the specific use case make the context sufficient for an agent to infer usage.

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

Deploy Server

Other Tools

search_aiA