Gemini DeepSearch MCP
Leverages Google Search to perform deep web research, generating queries and synthesizing information from search results
Uses Google Gemini models (Flash and Pro) to power automated research capabilities, with configurable effort levels for research depth
Utilizes LangGraph for workflow management and state tracking during the multi-step research process
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Gemini DeepSearch MCPresearch the latest quantum computing breakthroughs with high effort"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Gemini DeepSearch MCP
Gemini DeepSearch MCP is an automated research agent that leverages Google Gemini models and Google Search to perform deep, multi-step web research. It generates sophisticated queries, synthesizes information from search results, identifies knowledge gaps, and produces high-quality, citation-rich answers.
Features
Automated multi-step research using Gemini models and Google Search
FastMCP integration for both HTTP API and stdio deployment
Configurable effort levels (low, medium, high) for research depth
Citation-rich responses with source tracking
LangGraph-powered workflow with state management
Related MCP server: MCP Hub
Usage
Development Server (HTTP + Studio UI)
Start the LangGraph development server with Studio UI:
make devLocal MCP Server (stdio)
Start the MCP server with stdio transport for integration with MCP clients:
make localTesting
Run the test suite:
make testTest the MCP stdio server:
make test_mcpUse MCP inspector
make inspectWith Langsmith tracing
GEMINI_API_KEY=AI******* LANGSMITH_API_KEY=ls******* LANGSMITH_TRACING=true make inspectAPI
The deep_search tool accepts:
query (string): The research question or topic to investigate
effort (string): Research effort level - "low", "medium", or "high"
Low: 1 query, 1 loop, Flash model
Medium: 3 queries, 2 loops, Flash model
High: 5 queries, 3 loops, Pro model
Return Format
HTTP MCP Server (Development mode):
answer: Comprehensive research response with citations
sources: List of source URLs used in research
Stdio MCP Server (Claude Desktop integration):
file_path: Path to a JSON file containing the research results
The stdio MCP server writes results to a JSON file in the system temp directory to optimize token usage. The JSON file contains the same answer and sources data as the HTTP version, but is accessed via file path rather than returned directly.
Requirements
Python 3.12+
GEMINI_API_KEYenvironment variable
Installation
Install directly using uvx:
uvx install gemini-deepsearch-mcpClaude Desktop Integration
To use the MCP server with Claude Desktop, add this configuration to your Claude Desktop config file:
macOS
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"gemini-deepsearch": {
"command": "uvx",
"args": ["gemini-deepsearch-mcp"],
"env": {
"GEMINI_API_KEY": "your-gemini-api-key-here"
},
"timeout": 180000
}
}
}Windows
Edit %APPDATA%/Claude/claude_desktop_config.json:
{
"mcpServers": {
"gemini-deepsearch": {
"command": "uvx",
"args": ["gemini-deepsearch-mcp"],
"env": {
"GEMINI_API_KEY": "your-gemini-api-key-here"
},
"timeout": 180000
}
}
}Linux
Edit ~/.config/claude/claude_desktop_config.json:
{
"mcpServers": {
"gemini-deepsearch": {
"command": "uvx",
"args": ["gemini-deepsearch-mcp"],
"env": {
"GEMINI_API_KEY": "your-gemini-api-key-here"
},
"timeout": 180000
}
}
}Important:
Replace
your-gemini-api-key-herewith your actual Gemini API keyRestart Claude Desktop after updating the configuration
Set ample timeout to avoid
MCP error -32001: Request timed out
Alternative: Local Development Setup
For development or if you prefer to run from source:
{
"mcpServers": {
"gemini-deepsearch": {
"command": "uv",
"args": ["run", "python", "main.py"],
"cwd": "/path/to/gemini-deepsearch-mcp",
"env": {
"GEMINI_API_KEY": "your-gemini-api-key-here"
}
}
}
}Replace /path/to/gemini-deepsearch-mcp with the actual absolute path to your project directory.
Once configured, you can use the deep_search tool in Claude Desktop by asking questions like:
"Use deep_search to research the latest developments in quantum computing"
"Search for information about renewable energy trends with high effort"
Agent Source
The deep search agent is from the Gemini Fullstack LangGraph Quickstart repository.
License
MIT
Available Tools
1 tooldeep_searchC
Perform a deep search on a given query using an advanced web research agent.
Args: query: The research question or topic to investigate. effort: The amount of effect for the research, low, medium or hight (default: low).
Returns: A dictionary containing the file path to a JSON file with the answer and sources.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query string | |
| effort | No | Search effort | low |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'advanced web research agent' and returns a file path to JSON, but doesn't cover critical aspects like rate limits, authentication needs, execution time, or what 'deep' entails operationally. For a tool with no annotation coverage, this leaves significant behavioral traits undisclosed.
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 appropriately sized and front-loaded with the core purpose. The 'Args' and 'Returns' sections are structured but slightly verbose (e.g., 'low, medium or hight' has a typo). Overall, it's efficient with minimal waste, though not perfectly polished.
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?
Given the tool's complexity (web research with effort levels), no annotations, and an output schema present (implied by 'Returns' statement), the description is moderately complete. It covers the basic operation and return format but lacks details on behavioral traits and usage context, making it adequate but with clear gaps.
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?
The description adds minimal semantics beyond the input schema. It explains 'query' as 'the research question or topic to investigate' and 'effort' as 'the amount of effect for the research', but the schema already has 100% coverage with clear descriptions. The description's param info is redundant, so it meets the baseline of 3 without adding significant value.
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: 'Perform a deep search on a given query using an advanced web research agent.' It specifies the verb ('perform a deep search') and resource ('web research'), though it doesn't differentiate from siblings since none exist. The purpose is specific and actionable, not vague or tautological.
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 mentions 'advanced web research agent' but doesn't explain what makes it 'deep' or in what contexts it's preferred over other search methods. With no sibling tools, the lack of explicit usage context is a notable gap.
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. Dates show when Glama detected each change.
1 tool update
v1.0.0- Changed
deep_search3 fields changed- removed
Input schema / properties / effort / titleRemoved value: -"Effort" - removed
Input schema / properties / query / titleRemoved value: -"Query" - changed
Output schema / (root)Previous value: -nullNew value: +{ + "additionalProperties": true, + "type": "object" +}
1 tool update
- First observed
deep_search
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'deep_search' has a clear, distinct purpose focused on performing deep web research.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'deep_search' follows a clear verb_noun pattern and is descriptive of its function.
A single tool is generally too few for most server purposes, as it limits functionality and flexibility. While it might suffice for a very narrow scope, it feels thin and incomplete for a server named 'Gemini DeepSearch MCP', which suggests broader research capabilities.
The server is severely incomplete for a deep search/research domain. There are no tools for refining searches, managing search history, filtering results, or handling different types of queries. The single tool provides a basic search function but lacks the comprehensive coverage expected for a research-oriented server.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Web research for agents: quality-scored Google search, webpage extraction, and deep research.
Web search, fetch, extract, and research for AI agents. Markdown output + AI-synthesized answers.
Agent-native search engine with live web research optimized for AI agents.
Autonomous research agent that pays every source it cites in USDC on Arc via x402 micropayments.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables iterative deep research by integrating AI agents with search engines, web scraping, and large language models for efficient data gathering and comprehensive reporting.4323MIT
- AlicenseCqualityDmaintenanceA sophisticated research assistant that orchestrates a 5-step workflow of connected AI agents to provide deep research capabilities including question enhancement, web search, summarization, citation formatting, and result combination.11MIT
- AlicenseNot gradedqualityDmaintenanceA LangGraph-powered research agent that performs iterative web searches using Google Search and Gemini models to generate structured reports with citations. It integrates with MCP-compatible clients like Claude and Cursor to enable sophisticated, multi-step AI research workflows.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to perform professional-grade deep research by aggregating real-time data from multiple sources, evaluating source credibility, and generating comprehensive reports.311Apache 2.0
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/alexcong/gemini-deepsearch-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server