Gemini MCP Tool

Content

Gemini MCP Tool connects Claude to the Google Gemini CLI through a local stdio MCP server. It is designed for workflows where Claude should ask Gemini for a second-pass analysis, use Gemini's larger context window on selected files or directories, brainstorm alternatives, or request structured edit suggestions without leaving the MCP client.

The server exposes MCP tools and prompts from a unified registry. Current source registers ask-gemini, brainstorm, fetch-chunk, Ping, and Help tools, with test-only tools gated behind an environment variable. The ask-gemini implementation supports optional model selection, sandbox mode, change mode, and chunk continuation. The Gemini executor validates @ file references against the current working directory before passing prompts to the Gemini CLI.

Source Review

• https://github.com/jamubc/gemini-mcp-tool
• https://github.com/jamubc/gemini-mcp-tool/blob/main/README.md
• https://jamubc.github.io/gemini-mcp-tool/
• https://registry.npmjs.org/gemini-mcp-tool
• https://github.com/jamubc/gemini-mcp-tool/blob/main/package.json
• https://github.com/jamubc/gemini-mcp-tool/blob/main/src/index.ts
• https://github.com/jamubc/gemini-mcp-tool/blob/main/src/tools/index.ts
• https://github.com/jamubc/gemini-mcp-tool/blob/main/src/tools/ask-gemini.tool.ts
• https://github.com/jamubc/gemini-mcp-tool/blob/main/src/tools/fetch-chunk.tool.ts
• https://github.com/jamubc/gemini-mcp-tool/blob/main/src/utils/geminiExecutor.ts
• https://github.com/jamubc/gemini-mcp-tool/blob/main/LICENSE

These sources were reviewed on 2026-06-06. Prefer the live repository, README, docs site, npm registry metadata, package manifest, stdio server implementation, tool registry, ask-gemini implementation, Gemini CLI executor, chunk helper, and license file for current install paths, tool registration, sandbox behavior, file-reference handling, package metadata, and licensing.

Features

• Local stdio MCP server distributed as the gemini-mcp-tool npm package.
• Claude Code one-line setup through claude mcp add gemini-cli -- npx -y gemini-mcp-tool.
• Claude Desktop configuration through npx -y gemini-mcp-tool, or global gemini-mcp after package installation.
• MCP tools and prompts for asking Gemini, brainstorming, fetching chunked change-mode output, pinging the server, and showing help.
• Optional Gemini model selection, with the README documenting gemini-2.5-pro as the default.
• Optional Gemini CLI sandbox flag from the verified ask-gemini tool path.
• Change mode for structured OLD/NEW edit suggestions, including chunk cache retrieval for large responses.
• Working-directory checks for @ file references before prompts reach Gemini CLI's file-inlining parser.
• Unofficial third-party project with a non-commercial repository license text.

Installation

Install and configure the Google Gemini CLI first. Then add the MCP server to Claude Code:

claude mcp add gemini-cli -- npx -y gemini-mcp-tool

For Claude Desktop or another compatible MCP client, use the npm package through npx:

{
  "mcpServers": {
    "gemini-cli": {
      "command": "npx",
      "args": ["-y", "gemini-mcp-tool"]
    }
  }
}

Restart the MCP client after editing configuration, then use the client's MCP status view to confirm the gemini-cli server is active.

Use Cases

• Ask Gemini to summarize a large file, dependency manifest, or directory using the Gemini CLI @ reference syntax.
• Get a second-model review of code architecture, bug hypotheses, or refactor options while keeping Claude as the primary coding assistant.
• Use brainstorming prompts to compare approaches before changing a complex codebase.
• Request sandboxed Gemini CLI analysis for risky scripts, generated commands, package installs, or code experiments.
• Generate structured change-mode suggestions that Claude can inspect and apply in smaller chunks.
• Keep a local MCP workflow while using the separately installed Gemini CLI for authentication and provider access.

Safety and Privacy

Gemini MCP Tool is a bridge from Claude to another model provider path. Anything included in a prompt, selected through an @ reference, shown in terminal output, or summarized in a change-mode response can be sent through Gemini CLI under the user's configured Google account or API context.

Use the smallest useful file references, keep prompts inside the intended repository, and avoid secrets or regulated data. The source currently validates that @ references stay inside the working directory, but that does not make the selected project files safe to disclose. Review proposed OLD/NEW changes before applying them, and treat sandboxed runs as risk-reducing rather than risk-free.

The project is not affiliated with Google. Its package metadata and README describe MIT licensing, while the repository license text is non-commercial, so commercial users should review licensing with the project owner before adopting it.

Duplicate Check

Existing MCP content includes Google, search, code-analysis, and local CLI servers, but no dedicated gemini-mcp-tool, gemini-cli MCP bridge, or jamubc/gemini-mcp-tool entry was found in content/mcp. Gemini MCP Tool is distinct because it documents the npm-distributed stdio server that calls the Google Gemini CLI from Claude and exposes verified Gemini analysis, brainstorm, change-mode, and chunk-retrieval workflows.