Google CLI · stdio MCP · setup guide 04
Gemini CLI
connects locally.
Connect Gemini CLI to the local MCP server with mcpServers settings and try batched classification or Playwright browser inspection.
01 / Build once
Prepare the source checkout
npm install
npm run buildKeep the absolute checkout path ready. The published npm package is not available yet; when it ships, this setup will be shorter.
02 / Add the server
~/.gemini/settings.json or .gemini/settings.json
gemini mcp add --scope user agent-decision-kit node /absolute/path/to/agent-decision-kit/dist/cli.js mcp
gemini mcp listGemini CLI can configure stdio through both settings.json and its mcp management commands. Leave server trust disabled to preserve normal per-tool confirmation behavior.
Configuration option
Source-checkout server entry
{
"agent-decision-kit": {
"command": "node",
"args": [
"/absolute/path/to/agent-decision-kit/dist/cli.js",
"mcp"
]
}
}03 / Verify
Check the connection
Run `gemini mcp list` and check the `/mcp` view for the connected tool set.
04 / Try a real workflow
Start with sample data
Use screen_text to run two caller-provided yes/no checks on a sample sentence. Report the calibration label and caveat.
Client setup reference: Gemini CLI MCP guide ↗