Gemini Search MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_MODEL | No | Model to use: flash (gemini-2.5-flash, balanced), flash-lite (gemini-2.5-flash-lite, fastest/cheapest), or pro (gemini-2.5-pro, highest performance) | flash |
| GEMINI_API_KEY | Yes | Google AI API key (required). Can be obtained from https://aistudio.google.com/apikey | |
| GEMINI_WEB_SEARCH | No | Enable web search: true/false | true |
| GEMINI_THINKING_BUDGET | No | Thinking budget: -1=auto, 0=off, 1-24576 | -1 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gemini-searchB | An AI agent powered by Gemini 2.5 Flash with Google Search grounding. Useful for finding the latest information, troubleshooting errors, researching topics, and discussing ideas. Returns responses with cited sources from the web. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a clearly defined purpose focused on AI-powered search with web grounding.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'gemini-search' follows a clear and descriptive pattern.
A single tool is too few for a server named 'Gemini Search MCP', which suggests a broader search functionality scope. While the tool is powerful, the set feels thin and limited, lacking complementary operations like filtering, saving results, or managing search history.
The tool surface is severely incomplete for a search domain. It provides a general search function but lacks essential operations such as refining searches, handling pagination, accessing cached results, or integrating with other data sources, which are typical in search APIs.