gemini-cli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_BIN | No | Path to Gemini CLI binary | gemini |
| GEMINI_MODEL | No | Default model | gemini-2.5-flash |
| GEMINI_TIMEOUT | No | Idle timeout in ms (resets on each output chunk) | 120000 |
| GEMINI_SYSTEM_MD | No | Path to custom system prompt, or "default" for Gemini built-in | |
| GEMINI_MAX_RESPONSE | No | Max response chars before truncation | 100000 |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gemini_queryA | Send a prompt to Google Gemini via locally authenticated CLI. Supports all Gemini models. Use @path to reference local files. Options: sandbox mode, yolo (auto-approve), approval modes, extra directories. |
| gemini_infoB | Gemini CLI diagnostics: check connectivity, get version, list sessions or extensions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: gemini_info handles diagnostics and system information, while gemini_query handles querying the Gemini model. There is no overlap in functionality that could cause confusion.
Both tools follow a consistent gemini_ prefix pattern with clear descriptive suffixes (info and query). The naming is uniform and predictable across the toolset.
With only two tools, the server feels under-scoped for a CLI interface to Gemini. A typical CLI would include more operations like session management, configuration handling, or batch processing, making this set feel incomplete for the domain.
The toolset is severely incomplete for a Gemini CLI interface. It lacks essential operations such as managing sessions, configuring settings, handling file uploads beyond references, or listing available models. The two tools cover only basic diagnostics and querying, leaving significant gaps in typical CLI workflows.