Gemini CLI Integration

Quick Start

kicad-mcp-pro setup gemini

Or manually add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "kicad": {
      "command": "uvx",
      "args": ["kicad-mcp-pro"],
      "env": {
        "KICAD_MCP_PROJECT_DIR": "$PWD",
        "KICAD_MCP_PROFILE": "default",
        "KICAD_MCP_OPERATING_MODE": "readonly"
      },
      "cwd": ".",
      "timeout": 30000,
      "trust": false,
      "includeTools": [
        "kicad_get_project_info",
        "project_quality_gate",
        "run_erc",
        "run_drc",
        "validate_design"
      ]
    }
  }
}

Verification

/mcp  →  verify the kicad server is connected

Slash Prompt

Add to your Gemini repo instructions:

When the task involves KiCad, use the kicad MCP server. Default policy: inspect before editing. Run quality gates before suggesting release. Never run destructive tools without explicit user confirmation. Prefer read-only tools first.

Remote

{
  "mcpServers": {
    "kicad-cloud": {
      "httpUrl": "https://mcp.kicad.example.com/mcp",
      "timeout": 30000,
      "trust": false,
      "includeTools": ["search_kicad_knowledge", "analyze_uploaded_kicad_project"]
    }
  }
}

Gemini CLI extension pilot (opt-in)

A local, unsubmitted extension combines the MCP server connection with the seven generated Agent Skills. See integrations/gemini-cli/kicad-mcp-pro/. On a trusted developer machine where Gemini CLI and uvx are installed:

gemini extensions install ./integrations/gemini-cli/kicad-mcp-pro
gemini extensions list

Gemini copies local extension packages, so installed copies do not update when this repository changes. The extension defaults to readonly mode; a pre-existing settings.json entry can override its MCP server definition. Review that precedence before declaring the installation safe. A static manifest check is not real-host verification: follow the host smoke checklist and log the actual outcome.