Skip to main content
koppar is one file. It talks to the same tools as the MCP server and prints JSON on stdout, with progress on stderr, so a person and an agent can both use it.

Install

Needs Node.js 20 or newer.
It puts ~/.koppar/bin/koppar in place and tells you if that folder needs adding to your PATH. Run the same line again to update. Every deploy ships the CLI; there is no npm package.

Log in

KOPPAR_API_KEY and KOPPAR_URL override the saved login in ~/.config/koppar/config.json.

A design, end to end

koppar help lists every command.

Your own KiCad project

koppar help lists the rest of the board commands: outline, keepouts, zones, ripup, repair, polish, widen, tie, couple, diagnose, census, score, fill, cleanup, swap, add-files. See the MCP tools for what each one does.

Any tool, directly

As a local MCP server

For a client that only runs local servers:
koppar mcp-config prints the client configuration for both the local and the remote setup.