gemini-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CDP_URL | No | Chrome DevTools URL. If set, connects to existing Chrome instead of launching one | |
| HEADLESS | No | Set to 0 to show browser window | 1 |
| BROWSER_CHANNEL | No | Browser to use: chrome, msedge, chromium | chrome |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web using Google AI Mode and get a synthesized answer with sources. Uses Google Search's AI Mode (powered by Gemini) to search the web in real-time and return a comprehensive, grounded answer. Results include information from current web pages, news, and data. This is equivalent to using Google Search's "AI Mode" tab — the AI reads multiple web sources and synthesizes an answer, similar to Perplexity or Grok's web search, but powered by Google's search index. Args: query: Search query or question. Can be anything you'd type into Google. Examples: "latest news about AI regulation", "Bitcoin price today", "how does mRNA vaccine work", "Python asyncio best practices 2026" Returns: A synthesized answer based on real-time web search results. The answer is grounded in actual web content found by Google. |
| askA | Ask Google AI Mode any question and get an AI-generated answer. Similar to web_search but intended for general questions that may or may not require web search. Google AI Mode will automatically decide whether to search the web or answer from its training data. Args: prompt: Any question or instruction. Google AI Mode will search the web if needed and synthesize an answer. Returns: AI-generated answer, potentially grounded in web search results. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have distinct intentions: 'ask' for general questions that may use training data, and 'web_search' for explicit web-grounded answers. The description of 'ask' clarifies it is similar but flexible, reducing ambiguity. However, an agent might still be uncertain which to choose when a question could be answered from either source.
'ask' is a single verb, while 'web_search' is verb_noun with underscore. They do not follow a consistent pattern, which could be slightly confusing. However, both names are descriptive and readable.
With only 2 tools, the server feels thin for a search/QA domain. Typically a well-scoped server has 3-15 tools. However, for a specialized server focused on Google AI Mode, two tools (one for general questions and one for web search) might suffice, but it's on the lower end of acceptable.
The server covers two modes of AI-powered answering, but lacks a tool for pure training-data answers without web search, as 'ask' may still use web search. Users cannot force offline-only answers. Additionally, there is no tool for raw search results, only synthesized answers. This leaves notable gaps for a comprehensive search toolset.