Skip to main content
Glama
machinemates-ai

Gemini Research MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GEMINI_MODELNoModel for research_webgemini-3.7-flash
GEMINI_API_KEYYesGoogle AI Studio API key
FETCH_PROXY_URLNoDefault HTTP(S) proxy for fetch_webpage
DEEP_RESEARCH_AGENTNoDefault agent for research_deepdeep-research-preview-04-2026
GEMINI_SUMMARY_MODELNoModel for session summaries, titles, and clarificationgemini-3.7-flash
GEMINI_RESEARCH_HTTP_HOSTNoBind host for streamable-http. Non-loopback requires GEMINI_RESEARCH_HTTP_BEARER_TOKEN127.0.0.1
GEMINI_RESEARCH_HTTP_PATHNoURL path for streamable-http/mcp
GEMINI_RESEARCH_HTTP_PORTNoBind port for streamable-http8000
GEMINI_RESEARCH_TRANSPORTNostdio or streamable-httpstdio
GEMINI_RESEARCH_EXPORT_DIRNoDisk-first destination when export_research_session has no output_path~/.gemini-research/exports/
GEMINI_RESEARCH_STORAGE_URLNoRedis URL to share sessions/exports across multiple server instances/workers; falls back to local DiskStore when unset
GEMINI_RESEARCH_TTL_SECONDSNoOverride session/export TTL
GEMINI_RESEARCH_STORAGE_PATHNoCustom directory for the local DiskStore
GEMINI_RESEARCH_HTTP_BEARER_TOKENNoStatic bearer token required to call streamable-http. Never reuse GEMINI_API_KEY for this

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

CapabilityDetails
tasks
{
  "list": {},
  "cancel": {},
  "requests": {
    "tools": {
      "call": {}
    },
    "prompts": {
      "get": {}
    },
    "resources": {
      "read": {}
    }
  }
}
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
research_webA

Fast web research with Gemini grounding. Returns answer with citations in seconds.

Uses a fixed high thinking level for higher-quality grounded answers.

Use for: quick lookups, fact-checking, current events, documentation, "what is", "how to", real-time information, news, API references, error messages.

research_deepB

Run the default Deep Research agent with optional File Search and MCP tools.

resume_researchA

Resume an interrupted or in-progress research_deep session.

Use when a research_deep call was cut short (client disconnect, transport error, cancellation) or when you want to check whether a long-running session has since completed on Gemini's servers.

Because research_deep persists its session at the start, the research continues on Gemini's side even when the MCP client goes away — this tool retrieves the result once it's ready.

Call with no arguments to list recoverable sessions. Call with an interaction_id (returned by the original research_deep call or by list_research_sessions) to check a specific session's status; if it has completed, the full report is returned. Hand the result off to export_research_session(format="docx") to save the report to disk.

export_research_sessionA

Save (export, download, archive) a completed research session to a file on disk — Word (.docx), Markdown (.md), or JSON. Use this to recover your report after a research_deep run completes or is interrupted, and to convert reports into a shareable Word document.

Disk-first contract. The file is always written to disk, and the absolute path is returned on the first line of the response as Saved to: <path>. When output_path is omitted the file lands in GEMINI_RESEARCH_EXPORT_DIR (default ~/.gemini-research/exports/). An EmbeddedResource is still attached so GUI hosts can expose their native "Save As" affordance.

Similar to Google's Deep Research export feature, the DOCX output is a professional Word document suitable for sharing, archiving, or further editing.

Supported formats:

  • docx: Word document with headings, lists, and table of contents

  • markdown: Clean .md file with full report and citations

  • json: Machine-readable, all metadata preserved

Typical recovery flow:

  1. research_deep(...) completes (or is resumed via resume_research).

  2. export_research_session(format="docx") — no other arguments needed; the path on disk is returned in the response text.

search_toolsA

Search for tools using natural language.

Returns matching tool definitions ranked by relevance, in the same format as list_tools.

call_toolA

Call a tool by name with the given arguments.

Use this to execute tools discovered via search_tools.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
get_research_modelsList available research models and their capabilities. Returns information about the models used by this server: - Quick research model (Gemini + Google Search grounding) - Deep Research Agent (autonomous multi-step research)
Available ExportsList all currently cached exports ready for download.

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation4/5

Each tool has a distinct purpose: quick research vs deep research, resuming interrupted sessions, exporting results, and searching/calling tools. The descriptions clearly differentiate them, though research_web and research_deep could cause minor confusion if not carefully read.

Naming Consistency4/5

Tool names follow a mostly consistent verb_noun pattern in snake_case (research_web, research_deep, resume_research, export_research_session, search_tools, call_tool). The pattern is clear, though research_web and research_deep use qualifiers instead of straightforward nouns.

Tool Count5/5

6 tools is well-scoped for a research server. It covers quick research, deep research, session recovery, export, and tool discovery/execution without being overwhelming or sparse.

Completeness4/5

The tool surface covers the main research workflow: quick and deep research, resuming interrupted sessions, exporting results, and meta-tools for discovering and calling tools. Minor gaps like lack of a dedicated cancel or list historical sessions tool, but the set feels complete for most use cases.

Maintenance

ActivityMaintained
ResponsivenessNo issues