Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for gemini-mcp

Pod holds 16 of 17 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to gemini-mcp.

Most discussed

File analysis tools (gemini-analyze-document, gemini-summarize-pdf, etc.) not working

Description

File-accepting MCP tools are not functioning correctly. They either return errors about file access or produce empty/unusable responses.

Affected Tools

  • gemini-analyze-document
  • gemini-summarize-pdf
  • gemini-extract-tables
  • Any tool that accepts a filePath parameter

Steps to Reproduce

  1. Configure gemini-mcp in Claude Code
  2. Call any file analysis tool:
    gemini-analyze-document(filePath="/path/to/file.pdf", question="Summarize this document")
    

Read the thread · 2026-01-26 · closed · external user · 7 comments

Add configuration to limit the number tools that get loaded

There are so many tools it takes up too much space in agent's context :(

Read the thread · 2026-02-01 · closed · outside contributor · 5 comments

TypeScript compilation runs out of memory (OOM) even with 8GB heap

Description

Running tsc or bun run typecheck causes Node.js to run out of memory, even when allocating 8GB heap space.

Steps to Reproduce

# Default - crashes quickly
npx tsc --noEmit

# With increased heap - still crashes after ~2 minutes
NODE_OPTIONS="--max-old-space-size=8192" npx tsc --noEmit

Error Output

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Environment

  • Node.js 25.1.0
  • TypeScript

Read the thread · 2026-02-03 · closed · outside contributor · 4 comments

Latest version fails to connect from claude code

I have tried to setup the latest version utilizing claude code on my windows pc using an api key generated from the ai studio. After creating the project and grabbing the api key, this is the output of claude mcp list

gemini: env xxxxxxxxxxx VERBOSE=true npx -y https://github.com/rlabs-inc/gemini-mcp.gitp - ✗ Failed to connect

Read the thread · 2025-12-08 · closed · external user · 3 comments

CLI speak command uses uninitialized getOutputDir from gemini-client

Bug Description

The CLI speak command (src/cli/commands/speak.ts) imports getOutputDir from gemini-client.ts but never calls initGeminiClient() before using it. This means outputDir in gemini-client is uninitialized (empty string), causing the speak command to potentially write files to incorrect locations.

Current Behavior

// src/cli/commands/speak.ts line 11
import { getOutputDir } from '../gemini-client.js'

// line 172 - uses getOutputDir() without initiali

[Read the thread](https://github.com/RLabs-Inc/gemini-mcp/issues/13) · 2026-01-09 · closed · outside contributor · 2 comments

### Logger writes INFO messages to stdout, polluting JSON-RPC channel

## Problem

The logger in `utils/logger.js` uses `console.info()` for INFO-level messages. In Node.js, `console.info()` writes to **stdout**, which is the same channel used for JSON-RPC communication in stdio MCP servers.

This means the MCP client receives a mix of:

INFO: Starting MCP Gemini Server with model: gemini-3-pro-preview INFO: Logging mode: normal INFO: Output directory: /Users/... INFO: Connecting to Gemini API (attempt 1/3)... INFO: Successfully connected to Gemini API INFO: MCP

Read the thread · 2026-04-04 · open · external user · 1 comment

Running lint on the project really messes things up :)

My proposal:

  1. Run lint/prettier on the codebase
  2. add pre-commit hook to run typecheck/tests/lint before commit
  3. add a claude post edit hook that runs lint/prettier (including changes) after every change

@RodrigoLuglio give me the go ahead and I'll make this happen :)

Read the thread · 2026-02-01 · closed · outside contributor · 1 comment

"gemini-output" folder appears in project root

It should probably use a ~/.config/ (or platform appropriate) path that is unique for each project but not inside the project folder itself.

Be mindful of symlinks.

Read the thread · 2026-01-08 · closed · outside contributor · 1 comment

Most recent

Init connection test times out with Gemini 3 preview models (~18s response vs 10s timeout)

Problem

The init connection test in gemini-client.js has a hardcoded 10-second timeout (line 57), but Gemini 3 preview models (gemini-3-flash-preview, gemini-3-pro-preview) regularly take 15-20 seconds to respond to the first generateContent call.

This causes the MCP server to fail initialization on every attempt:

INFO: Connecting to Gemini API (attempt 1/3) using gemini-3-flash-preview...
WARN: Connection attempt 1 failed: Connection timeout
INFO: Connecting to Gemini API (att

[Read the thread](https://github.com/RLabs-Inc/gemini-mcp/issues/29) · 2026-04-04 · open · external user · 0 comments

### gemini-list-caches returns empty despite active caches existing

## Description

`gemini-list-caches` returns "No active caches found" even when caches are active and queryable via `gemini-query-cache`.

## Reproduction

1. Create a cache:

gemini-create-cache filePath="" displayName="test-cache" ttlMinutes=1440

Returns success with cache name and expiration.

2. Query the cache — works perfectly:

gemini-query-cache cacheName="test-cache" question="Summarize this document"

Returns correct results with cached token 

[Read the thread](https://github.com/RLabs-Inc/gemini-mcp/issues/26) · 2026-02-22 · open · external user · 0 comments

### npm install from GitHub fails due to husky prepare script

## Summary

**This does not affect the standard installation method** (`npx -y @rlabs-inc/gemini-mcp`) which works fine since the published npm package includes pre-built dist/ files.

This only affects git-based installs (`npm i -g rlabs-inc/gemini-mcp`).

## Problem

PR #20 changed the `prepare` script from `bun run build` to just `husky`, which broke git-based installs in two ways:

1. `husky` fails because it's not installed yet (it's a devDependency)
2. The build step was removed, so `dist/

[Read the thread](https://github.com/RLabs-Inc/gemini-mcp/issues/24) · 2026-02-04 · closed · outside contributor · 0 comments

### Add gemini-analyze-image tool for image analysis with bounding boxes and measurements

## Enhancement Request Analysis

Inspired by [this reddit post](https://old.reddit.com/r/ClaudeCode/comments/1q637ae/i_use_gemini_with_claude_code_to_allow_it_to_see/).

**Questions for Reporter**

| Question | Answer |
| ---------- | -------- |
| What specific types of measurements are most important for your use case (e.g., object dimensions, distances between objects, color analysis)? | all of them - anything that can be returned by the model|
| Should bounding box coordinates be returned in 

[Read the thread](https://github.com/RLabs-Inc/gemini-mcp/issues/9) · 2026-01-07 · closed · outside contributor · 1 comment

### Enforce time window requirement during category creation for both manual and ai-chat

Scheduling failed: Invalid scheduling request: Category "Music" has no time windows defined

[Read the thread](https://github.com/RLabs-Inc/gemini-mcp/issues/8) · 2025-12-20 · closed · external user · 0 comments

### Init connection test ignores GEMINI_MODEL, always uses pro model (causes 429 on free tier)

## Problem

  The `initGeminiClient` function in `gemini-client.ts` always uses `proModelName` for the connection test, regardless of the `GEMINI_MODEL` environment variable:

typescript await genAI.models.generateContent({ model: proModelName, // Always uses pro, ignores GEMINI_MODEL contents: 'Test connection', })


  This means users who set GEMINI_MODEL=gemini-2.0-flash to use the higher free tier limits (1500 req/day vs 50 req/day for pro) still get 429 errors on start

[Read the thread](https://github.com/RLabs-Inc/gemini-mcp/issues/7) · 2025-12-09 · closed · external user · 1 comment

### Default models point to non-existent experimental versions

## Issue

The default models in the codebase are set to experimental versions that no longer exist:
- `gemini-2.5-pro-exp-03-25`
- `gemini-2.0-flash-001` 
- `gemini-2.5-pro-preview-03-25`

This causes the MCP server to fail on connection when no model environment variables are provided.

## Error

models/gemini-2.5-pro-exp-03-25 is not found for API version v1beta, or is not supported for generateContent


## Solution
Update the defaults to the latest stable models documented in the offici

[Read the thread](https://github.com/RLabs-Inc/gemini-mcp/issues/4) · 2025-08-23 · closed · external user · 0 comments

### How do I remove this server?

I can see the server is added:

% claude mcp list gemini: env GEMINI_API_KEY= npx -y https://github.com/rlabs-inc/gemini-mcp.git


But I cannot remove it:

% claude mcp remove gemini No local MCP server found with name: gemini


I tried to ask Claude for help, but even Claud couldn't help me...

[Read the thread](https://github.com/RLabs-Inc/gemini-mcp/issues/2) · 2025-06-12 · closed · external user · 1 comment

The remaining reports are on [the project's issue tracker](https://github.com/RLabs-Inc/gemini-mcp/issues).