KiCad MCP Pro

KiCad MCP Pro runs locally from a Python package published to PyPI: kicad-mcp-pro version 3.37.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx kicad-mcp-pro. It reads the environment variable KICAD_MCP_LOG_LEVEL; set it in the client's configuration for this server.

KiCad MCP Pro runs locally from a Node.js package published to the npm registry: kicad-mcp-pro version 3.37.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y kicad-mcp-pro@3.37.0. It reads the environment variable KICAD_MCP_PRO_PYPI_VERSION; set it in the client's configuration for this server.

KiCad MCP Pro runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/oaslananka/kicad-mcp-pro:3.37.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm ghcr.io/oaslananka/kicad-mcp-pro:3.37.0. Required arguments: image.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "kicad-mcp-pro": {
      "command": "uvx",
      "args": [
        "kicad-mcp-pro"
      ],
      "env": {
        "KICAD_MCP_LOG_LEVEL": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect