by alexcong
Gemini DeepSearch automates web research using Google Search API and Gemini models, delivering in-depth, cited insights
Performs automated multi-step web research using Google Search and Gemini AI to generate comprehensive answers with citations. Configurable research depth levels control query generation and iteration loops.
Gemini DeepSearch is a community-built MCP server published by alexcong that provides AI assistants with tools and capabilities via the Model Context Protocol. Gemini DeepSearch automates web research using Google Search API and Gemini models, delivering in-depth, cited insights It is categorized under search web, ai ml.
You can install Gemini DeepSearch in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Gemini DeepSearch is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Fetch and extract information from websites automatically
Example
Research competitor pricing, scrape product reviews, monitor news mentions
Automate 5-10 hours/week of manual web research
Track website changes, new content, price updates
Example
Monitor competitor blog for new posts, track stock availability, watch for pricing changes
Stay informed without manual checking, never miss important updates
Extract structured data from multiple websites
Example
Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data
Build datasets 100x faster than manual copying
Share your MCP server with the developer community
We evaluated Gemini DeepSearch against two servers with overlapping tools; this profile had the clearer scope statement.
We wired Gemini DeepSearch into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We wired Gemini DeepSearch into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Gemini DeepSearch is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Gemini DeepSearch has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Strong directory entry: Gemini DeepSearch surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Gemini DeepSearch is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Gemini DeepSearch is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Gemini DeepSearch is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We wired Gemini DeepSearch into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
showing 1-10 of 70
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.
Start the LangGraph development server with Studio UI:
make dev
Start the MCP server with stdio transport for integration with MCP clients:
make local
Run the test suite:
make test
Test the MCP stdio server:
make test_mcp
Use MCP inspector
make inspect
With Langsmith tracing
GEMINI_API_KEY=AI******* LANGSMITH_API_KEY=ls******* LANGSMITH_TRACING=true make inspect
The deep_search tool accepts:
HTTP MCP Server (Development mode):
Stdio MCP Server (Claude Desktop integration):
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.
GEMINI_API_KEY environment variableInstall directly using uvx:
uvx install gemini-deepsearch-mcp
To use the MCP server with Claude Desktop, add this configuration to your Claude Desktop config file:
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
}
}
}
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
}
}
}
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:
your-gemini-api-key-here with your actual Gemini API keyMCP error -32001: Request timed outFor 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:
The deep search agent is from the Gemini Fullstack LangGraph Quickstart repository.
MIT
Interact with services that don't offer APIs
Example
Check form submissions, validate website functionality, test user flows
Automate interactions with any website, even without API
Prerequisites
Time Estimate
20-40 minutes including configuration and testing
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
Compatibility
✓ Use when
Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.
✗ Avoid when
Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.