Gemini CLI Orchestrator MCP

Gemini CLI Orchestrator v2.0 - Sequential Thinking MCP

A metaprompting-first MCP server that guides AI agents through intelligent, multi-step codebase analysis using Google's Gemini AI.

🧠 Core Philosophy

Don't build intelligence into the system. Build prompts that elicit intelligence from the agent.

This tool doesn't wrap or replace your thinking - it guides you to think more systematically about complex codebase analysis through structured workflows.

🚀 Quick Start

Step 1: Install Gemini CLI

Step 2: Authenticate (one-time setup)

Step 3: Install this tool

Step 4: Test it works

Step 5: Try your first analysis (using Claude Code CLI)

That's it! Authentication is handled automatically by the gemini CLI.

How It Works

Instead of trying to be "smart" about your analysis, this tool provides four simple tools that guide you through systematic analysis:

🎯 gemini_plan_analysis(goal)

Breaks down complex analysis goals into a step-by-step plan. Be specific about what you want to understand and why.

Example:

🔍 gemini_craft_prompt(step_description, context)

Helps you write better prompts for Gemini by suggesting effective commands and context for each analysis step.

Example:

🔄 gemini_iterate_analysis(current_understanding, iteration_goal)

Guide iterative analysis using observe-think-act cycles for dynamic problem-solving.

Example:

📊 gemini_synthesize_findings(steps_summary, synthesis_goal)

Combine insights from multiple analysis steps into comprehensive understanding.

Example:

Example Workflow

Here's how you'd conduct a security audit using the orchestrator:

🎯 Key Benefits

✅ Simplified Authentication - Uses your existing gemini CLI setup
✅ True Metaprompting - Guides your intelligence, doesn't replace it
✅ Multi-Step Analysis - Break complex problems into manageable steps
✅ Flexible Workflows - Adapt your approach based on what you discover
✅ Direct Gemini Integration - No wrapper complexity or auth overhead

📚 Documentation

• How It Works - Deep dive into the architecture and metaprompting philosophy
• Contributing Guide - How to contribute to the project
• Code of Conduct - Community standards and expectations

🤝 Contributing

We welcome contributions! Please see our Contributing Guide and Code of Conduct for details on how to get involved.

MCP Configuration

🚨 Important Note for Existing Users

If you've previously installed this MCP server (especially if you used gemini-orchestrator.mjs), you may have cached configurations. The filename was renamed to gemini-collaboration-guide.mjs for clarity. See "Handling Previous Installations" below if you encounter setup issues.

Claude Code CLI (Recommended)

The easiest and most reliable way to configure the MCP server:

Important:

• Use the full absolute path to the gemini-collaboration-guide.mjs file
• The server name must be exactly gemini-collaboration-guide
• Restart Claude Code after adding the server

Handling Previous Installations / Filename Changes

If you previously configured this MCP server or encounter issues like "Status: ✘ failed", follow these steps:

Manual Configuration (Alternative)

If you prefer manual JSON configuration:

Claude Desktop - Config file: ~/Library/Application Support/Claude/claude_desktop_config.json

Cursor IDE - Config file: .cursor/mcp.json

Windsurf IDE - Config file: windsurf_config.json

Troubleshooting

If /mcp shows "No MCP servers configured" or tools aren't available:

1. Check for filename/configuration conflicts (Most Common Issue)
   • Follow the "Handling Previous Installations" section above
   • The file was renamed from gemini-orchestrator.mjs to gemini-collaboration-guide.mjs
2. Clean setup process:
   # Remove all old configurations claude mcp remove gemini-cli-orchestrator claude mcp remove gemini-orchestrator claude mcp remove gemini-collaboration-guide # Add with correct filename claude mcp add gemini-collaboration-guide node /absolute/path/to/gemini-collaboration-guide.mjs
3. Verify the file exists:
   ls -la /path/to/your/gemini-cli-orchestrator/gemini-collaboration-guide.mjs
4. Test the server can start:
   node /path/to/your/gemini-cli-orchestrator/gemini-collaboration-guide.mjs --help
5. Restart Claude Code completely after any configuration changes
6. Verify success:
   claude mcp list # Should show: gemini-collaboration-guide /mcp # Should show the four tools

Common Errors:

• Status: ✘ failed → Usually wrong filename (use gemini-collaboration-guide.mjs)
• File does not exist → Check absolute path is correct
• Tools not appearing → Restart Claude Code after configuration

Advanced Usage Examples

Security Audit Workflow

Performance Analysis Workflow

Architecture Review Workflow

File Pattern Examples

Use glob patterns to focus analysis on relevant files:

Requirements

• Node.js 18+
• Google Gemini CLI installed and authenticated
• Basic understanding of glob patterns

Troubleshooting

"Command not found: gemini"

"Authentication failed"

"No files found"

What's New in v2.0

🎉 Complete architectural redesign - From complex wrapper to simple orchestrator
🎉 Eliminated authentication complexity - Uses native gemini CLI auth
🎉 True metaprompting approach - Guides intelligence instead of replacing it
🎉 Sequential thinking workflows - Multi-step analysis with state management
🎉 Simplified setup - No complex configuration or environment variables

Philosophy

This tool embodies the metaprompting principle: trust agent intelligence over system complexity.

Instead of trying to be smart about your analysis, it provides simple tools that guide you to think systematically about complex problems. The result is more thoughtful analysis and better insights.

Perfect for leveraging Gemini's massive context window through intelligent, structured workflows.