Gemini Research MCP Server
Related Servers
Alternatives to Gemini Research MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that runs Google Gemini Deep Research using live Chrome session cookies, enabling autonomous web research and cited report generation without an API key.3MIT
- AlicenseAqualityBmaintenanceAn MCP server that exposes Gemini's Deep Research Agent for comprehensive web research.262 npm46 PyPI4MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that utilizes LangGraph and Google Gemini to conduct comprehensive research through multi-iteration deep searches and quick results. It provides high-quality analysis with automated citations and grounding metadata for thorough investigations.2MIT
- AlicenseNot gradedqualityDmaintenanceIntegrates Gemini API research capabilities (Deep Research, Quick Search, URL Analysis) into a unified MCP server, enabling comprehensive research, web search, and URL analysis through natural language.MIT
- AlicenseAqualityFmaintenanceMCP server for web search powered by Google AI Mode (Gemini). Enables any AI agent to search the web in real-time for free and without rate limits.2186MIT
- AlicenseAqualityCmaintenanceMCP server for Google's Gemini API, enabling text, image, video, speech, embeddings, and deep research capabilities through a single tool set.10197 npmMIT
TDQS
Scored across 9 tools
The research tools are mostly distinguishable by depth, latency, and explicit use-case guidance, but research_run, research_deep, research_deep_max, and research_web have nuanced overlapping intent. The generic search_tools/call_tool pair is clear as meta-tools but sits outside the research workflow.
All names use snake_case and are readable, with a clear research_* family and verb_noun-style lifecycle/meta tools. The convention is not perfectly uniform because some tools use noun-prefixed research_* names while others start with a verb, but this is a minor deviation.
Nine tools is well-scoped for a research server with quick web lookup, deep research variants, comparison, resume/export lifecycle, and meta-tool discovery. Each tool appears to serve a distinct workflow rather than inflating the surface unnecessarily.
The surface covers research web/deep/max/compare, resume, and export, but research_run explicitly relies on get_research_run, which is not present, leaving background research jobs with no stated way to inspect or recover results. Similarly, resume_research references list_research_sessions, which is absent from the tool set.