Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/oaslananka/kicad-mcp-pro/quickstartgit clone --depth 1 https://github.com/oaslananka/kicad-mcp-proWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/oaslananka/kicad-mcp-pro/quickstart)<a href="https://agentmods.dev/agents/oaslananka/kicad-mcp-pro/quickstart"><img src="https://agentmods.dev/badge/agents/oaslananka/kicad-mcp-pro/quickstart.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00630 |
| Opus 5 | $0.00000 | $0.00315 |
| Sonnet 5 | $0.00000 | $0.00126 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
quickstart scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent quickstart matrix
Use this page when you want to connect one MCP-capable client quickly and start with a safe read-only KiCad workflow.
Recommended first prompt
Open the current KiCad project, inspect the schematic hierarchy, list ERC-relevant issues, render a schematic preview, and explain what changed without modifying files.
Keep the first run read-only. Switch to write mode only after the project is backed up and you are ready to review every modification.
Client matrix
| Client | Setup doc | Config location | First validation |
|---|---|---|---|
| Claude Desktop | Claude Desktop | claude_desktop_config.json |
Ask Claude to inspect the current project without editing files. |
| Cursor | Cursor | .cursor/mcp.json |
Use Agent mode and ask for a read-only ERC/DRC summary. |
| VS Code / Copilot | VS Code Copilot | .vscode/mcp.json |
Command Palette → MCP: List Servers. |
| Windsurf | Windsurf | ~/.codeium/windsurf/mcp_config.json |
Confirm the Cascade MCP panel shows the kicad server. |
| Cline | Cline | Cline MCP settings or ~/.cline/mcp.json |
Confirm the Cline panel lists the server and tools. |
| OpenCode | OpenCode | opencode.json |
Run opencode mcp list. |
Copy-paste baseline config
Use readonly for the first connection:
{
"mcpServers": {
"kicad": {
"command": "uvx",
"args": ["kicad-mcp-pro"],
"env": {
"KICAD_MCP_PROJECT_DIR": "/absolute/path/to/kicad/project",
"KICAD_MCP_PROFILE": "default",
"KICAD_MCP_OPERATING_MODE": "readonly"
}
}
}
}
VS Code / Copilot uses servers instead of mcpServers; see the dedicated page for the exact shape.
Expected output
A healthy first run should give the agent enough context to summarize:
- the active KiCad project or project path;
- schematic hierarchy and available board files;
- ERC/DRC-relevant findings when available;
- preview/render status when the runtime can produce visual evidence;
- clear warnings if KiCad CLI, project files, or rendering dependencies are unavailable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 62 lines · 0 tokens per session scan A a05f7e78b190
quickstart is an agent published in the GitHub repository oaslananka/kicad-mcp-pro (64 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 630 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
index
This section centralizes the instructions and client configuration surfaces used by coding agents and MCP-capable clients that work with KiCad Studio Kit.
client-configs
KiCad MCP Pro supports local stdio and Streamable HTTP MCP transports. The canonical copyable examples live under examples/mcp-clients/.
codex-support
KiCad Studio Kit supports Codex through the external MCP client path.
bom-reviewer
You are a reviewer subagent. Your job is to independently verify a BOM artifact produced by the circuit-design skill. You have access to all KiCad MCP tools.
code-reviewer
Use this agent when a major code change to the MCP server itself has been completed and needs to be reviewed against the original plan and project coding standards.
schematic-plan-reviewer
You are a reviewer subagent. Your job is to independently verify a schematic placement and wiring plan artifact. You have access to all KiCad MCP tools.