Gemini
Call Google Gemini models from Claude Code as MCP tools without leaving your agent workflow.
Overview
io.github.PavelGuzenfeld/gemini is a Build-phase MCP server that exposes Google Gemini as callable tools inside Claude Code.
What is this MCP server?
- Stdio MCP server (npm package claude-gemini-mcp) for local Claude Code wiring
- Exposes Google Gemini as agent-invokable tools over MCP
- Requires GEMINI_API_KEY as a secret environment variable
- Version 0.1.2 with Model Context Protocol server.schema.json 2025-12-11
- Open-source source on GitHub (PavelGuzenfeld/gemini-mcp)
- Server version 0.1.2
- 1 npm package (claude-gemini-mcp) with stdio transport
- 1 required secret env var: GEMINI_API_KEY
What problem does it solve?
Claude Code cannot reach Gemini natively, so you end up copy-pasting between chats or maintaining one-off API scripts.
Who is it for?
Indie developers standardizing on Claude Code who want Gemini as a supplemental model via MCP.
Skip if: Teams that only use Cursor or Codex without MCP stdio support, or anyone unwilling to manage a Google API key.
What do I get? / Deliverables
After registration, your agent can invoke Gemini through MCP tools using your GEMINI_API_KEY in the same Claude Code session.
- Gemini model tools callable from Claude Code over MCP
- Configured stdio MCP server entry with secret API key handling
Recommended MCP Servers
Journey fit
How it compares
MCP LLM bridge, not a standalone agent skill or chat UI.
Common Questions / FAQ
Who is io.github.PavelGuzenfeld/gemini for?
Claude Code users who want Google Gemini available as MCP tools during coding sessions.
When should I use io.github.PavelGuzenfeld/gemini?
Use it during the Build phase when you need Gemini-backed tool calls from your primary Claude Code agent.
How do I add io.github.PavelGuzenfeld/gemini to my agent?
Install the npm package claude-gemini-mcp, set GEMINI_API_KEY, and register the stdio MCP server in your Claude Code MCP config.