gemini-cli-mcp
<div align="center">
<img src="./assets/banner.svg" alt="Gemini CLI MCP Banner" width="100%" />
# π€ Gemini CLI MCP Server
_Seamless AI-to-AI Delegation via Local Gemini CLI_
[](https://www.npmjs.org/package/@cainmaila/gemini-cli-mcp)
[](https://opensource.org/licenses/MIT)
[](#requirements)
[**English**](./README.md) Β· [**ηΉι«δΈζ**](./README.zh-TW.md)
</div>
---
## π Why Gemini CLI MCP?
`gemini-cli-mcp` is an advanced Model Context Protocol (MCP) server that empowers your AI assistants by delegating complex tasks to your locally installed Gemini CLI.
Rather than collapsing failures into generic errors, this server returns **structured results along with execution metadata**, making it an essential tool for robust AI-to-AI handoffs and deep debugging.
### β¨ Key Features
- **π Zero-Friction Auth**: Transparently utilizes your existing local Gemini CLI setup and credentials.
- **π Standard MCP Ready**: Runs headless over `stdio`, effortlessly integrating with standard MCP client setups.
- **π οΈ Task-Oriented & Flexible**: Choose `executeTask` for direct answers, or drop down to `executePrompt` for precise control.
- **π¨ Native Image Generation**: Harnesses your local `nanobanana` extension to generate and retrieve images seamlessly.
- **π Environment Inspection**: Instantly discover available commands, extensions, skills, and MCP servers on the local machine.
---
## π¦ Installation
For normal usage, install the published package globally or run it through your package manager. Ensure you have [Node.js 18.18+](https://nodejs.org/) installed along with a configured local Gemini CLI.
```bash
# npm
npm install -g @cainmaila/gemini-cli-mcp
# pnpm
pnpm add -g @cainmaila/gemini-cli-mcp
# one-off execution without a global install
npx -y @cainmaila/gemini-cli-mcp
```
The published package name is `@cainmaila/gemini-cli-mcp`, but the installed executable name is `gemini-cli-mcp`.
If you use `pnpm add -g`, make sure your MCP client can see your `PNPM_HOME`/global bin directory. Some desktop MCP clients do not inherit the same `PATH` as your interactive shell, which can make `gemini-cli-mcp` look missing even though the package is installed.
If you want to work on this repository itself instead of using the published package, use the local development flow in [DEVELOPMENT.md](DEVELOPMENT.md).
---
## π Quick Start & Usage
### Running the Server
Since this is an MCP server, it is designed to communicate over `stdio` and should be launched by your MCP client.
```bash
gemini-cli-mcp
```
### Client Configuration Example
Add the following to your AI assistant's MCP configuration:
```json
{
"mcpServers": {
"gemini-cli": {
"command": "gemini-cli-mcp"
}
}
}
```
If your MCP client cannot resolve global binaries reliably, use one of these alternatives instead:
```json
{
"mcpServers": {
"gemini-cli": {
"command": "npx",
"args": ["-y", "@cainmaila/gemini-cli-mcp"]
}
}
}
```
```json
{
"mcpServers": {
"gemini-cli": {
"command": "node",
"args": ["/absolute/path/to/installed/package/build/index.js"]
}
}
}
```
Running `gemini-cli-mcp` directly in a terminal is only useful as a smoke test. It will wait for MCP traffic over `stdio`, so it may look idle until a client connects.
---
## π οΈ Available Tools
<details>
<summary><b><code>executeTask</code> (Recommended)</b></summary>
Best for upstream AI systems. Hands off a task to the Gemini CLI and returns a ready-to-use answer. Auto-applies edit approvals when necessary!
**Input Example:**
```json
{
"task": "Query today's weather in Taipei and provide a short summary.",
"expectedOutput": "Direct answer, no intro.",
"timeoutMs": 180000
}
```
**Output Example:**
```json
{
"answer": "...",
"ok": true,
"stdout": "...",
"stderr": "...",
"exitCode": 0,
"elapsedMs": 23053
}
```
</details>
<details>
<summary><b><code>executePrompt</code></b></summary>
A lower-level interface designed for callers who demand exact prompt control.
**Input Example:**
```json
{
"prompt": "Summarize the current repository",
"model": "gemini-2.5-pro",
"timeoutMs": 60000
}
```
**Output Example:**
```json
{
"ok": true,
"finalText": "...",
"stdout": "...",
"stderr": "",
"exitCode": 0,
"elapsedMs": 1532
}
```
</details>
<details>
<summary><b><code>executeImageTask</code></b></summary>
Flawless image-generation backed by the local `nanobanana` extension. Bypasses interactive prompts automatically!
**Input Example:**
```json
{
"prompt": "a cute orange cat portrait, clean light background",
"count": 1,
"timeoutMs": 180000
}
```
**Output Example:**
```json
{
"ok": true,
"responseText": "/path/to/project/nanobanana-output/cat.png",
"imagePaths": ["/path/to/project/nanobanana-output/cat.png"],
"primaryImagePath": "/path/to/project/nanobanana-output/cat.png",
"exitCode": 0,
"elapsedMs": 12000
}
```
</details>
<details>
<summary><b><code>inspectGeminiCli</code></b></summary>
Discover your AI environment's capabilities on the fly. Returns top-level commands, installed extensions, available skills, and configured MCP servers.
**Input Example:**
```json
{
"includeModelReportedTools": true,
"timeoutMs": 60000
}
```
</details>
---
## βοΈ Environment Overrides
Tailor the server to your specific environment simply by setting these variables:
| Variable | Description | Default |
| -------------------- | ---------------------------------- | --------- |
| `GEMINI_CLI_PATH` | Path to the Gemini executable | `gemini` |
| `GEMINI_PROMPT_FLAG` | The flag used for passing prompts | `-p` |
| `GEMINI_MODEL_FLAG` | The flag used to specify the model | `--model` |
---
## π Notes & Contributing
- **Authentication**: This server relies on your existing local Gemini CLI authentication.
- **Resilience**: If the local CLI is missing or broken, you will receive structured failure detailsβnever a silent crash.
- **Want to build with us?** Check out our developer guide in [DEVELOPMENT.md](DEVELOPMENT.md).
<br/>
<div align="center">
<i>Built for the next generation of AI collaboration.</i>
</div>
TDQS
Scored across 4 tools
executeTask and executePrompt overlap heavily: both accept text input and return results plus metadata, with only vague wording about 'task' versus 'prompt' to distinguish them. executeImageTask and inspectGeminiCli are clearly distinct, but the two execution tools create real selection ambiguity.
Three tools follow an execute* pattern and one uses inspect*, all in consistent camelCase. The pattern is readable and predictable, with the minor deviation being 'inspectGeminiCli' referring to a product rather than a generic action object.
Four tools is well-scoped for a Gemini CLI wrapper: prompt execution, task execution, image generation, and introspection. Each tool earns its place without unnecessary bloat.
The set covers the primary workflows of running prompts, executing tasks, generating images, and inspecting the CLI environment. Minor gaps exist around configuration or extension management, but the core use cases are well covered.