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 |
| GEMINI_SEARCH_CDP_PORT | No | CDP port used for self-launched Chrome | 19250 |
| GEMINI_SEARCH_CHROMEDRIVER | No | Chromedriver executable used by the undetected backend | |
| GEMINI_SEARCH_PROXY_SERVER | No | Chrome proxy server, e.g. socks5://127.0.0.1:7897 | |
| GEMINI_SEARCH_USER_DATA_DIR | No | Persistent Chrome profile directory. Reuses cookies across runs and is not deleted on shutdown | |
| GEMINI_SEARCH_BROWSER_BACKEND | No | Browser launcher: subprocess or undetected | subprocess |
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 tools 'ask' and 'web_search' have nearly identical descriptions, both using Google AI Mode and returning AI-generated answers. The only distinction is that 'ask' may optionally skip web search, but this is unclear and overlapping, making it hard for an agent to choose reliably.
Tool names 'ask' (verb) and 'web_search' (noun with underscore) do not follow a consistent pattern. Mixing a simple verb with a compound noun creates inconsistency, and no clear naming convention is evident across the set.
With only 2 tools, the server feels thin for a search service, but it is scoped to Google AI Mode. The count is borderline; it lacks additional tools for raw results or specialized searches, but the core functionality is covered.
For the narrow purpose of AI-powered search with synthesis, the server covers asking general questions and web searches. Minor gaps exist (e.g., no way to get unsynthesized results), but overall the surface is reasonably complete for its stated domain.