Skip to main content

​
How This Setup Works

Gemini CLI does not run the Monk extension itself. The setup has two parts:
  1. Keep Monk running in a supported IDE with MCP enabled for the project
  2. Open Gemini CLI in the same project so it can read the generated project settings

​
Step 1: Enable Monk MCP on the Monk Side

Monk MCP is not enabled by default. Before you open Gemini CLI, make sure Monk is already running in VS Code, Cursor, Windsurf, or Antigravity with the same project open. Make sure:
  • Monk is installed in one supported IDE that is currently running
  • the project is open in that IDE
  • you ran Monk: Manage MCP Server
  • you chose Enable MCP server
If you are choosing targets manually, include Gemini / Antigravity for this workspace. Monk writes the Gemini project config for you in .gemini/settings.json. Read more: Install Monk, MCP Getting Started

​
Step 2: Let Gemini CLI Load Monk

Gemini CLI supports project-scoped MCP configuration in .gemini/settings.json. Monk writes that file for you, so the next step is to open the same project in Gemini CLI.

​
Step 3: Verify That Monk Is Configured

Gemini CLI documents a command for listing configured MCP servers: 
gemini mcp list
You should see Monk in the server list for the current project.

​
Step 4: Approve Monk Tool Usage

Gemini CLI supports MCP trust and confirmation controls. By default, MCP servers are not trusted, which means Gemini will ask for confirmation before using Monk’s tools. That is the safest default and a good place to start. Gemini’s docs also describe:
  • server-level trust
  • tool-level allow-listing
  • project-scoped configuration as the default scope for MCP additions
Read more: Gemini CLI MCP docs

​
Step 5: Use Monk from Gemini CLI

Once Monk appears in the server list, Gemini CLI can use Monk for requests like:
  • analyze this project with Monk
  • use Monk to deploy this app
  • ask Monk what infrastructure is needed
  • use Monk to inspect logs and runtime health

​
If Monk Does Not Appear

  • confirm Monk is running in VS Code, Cursor, Windsurf, or Antigravity
  • confirm Monk MCP is enabled there for this workspace
  • confirm that supported IDE still has the project open
  • confirm Gemini CLI is running in the same project root
  • run gemini mcp list again
  • check whether your Gemini config has mcp.allowed or mcp.excluded rules that block Monk