HeyPCB for AI agents：一个MCP服务器，提供Claude代码、Codex、光标，claude.ai 一位PCB工程师。NPX -y @heypcb/MCP
概览
HeyPCB为AI代理服务。将HeyPCB添加到Claude代码、Codex、光标或Claude桌面，并从代理处设计真正的KiCad板：HeyPCB的服务器负责工程（Inky的设计代理、零件、布局、布线、DRC/ERC、晶圆检测），你的代理调用一些高级工具，如build_board、get_board、check_board导出和导出。或者你的代理用HeyPCB的零件库设计电路板本身，包含经过验证的电路模块和检查：search_parts、get_part、add_parts、add_block、Connect、get_netlist及其他零件和电路工具，然后用set_board_outline、set_board_rules、move_part、lock_parts、add_ground_pour和get_board_layout进行布局，按照check_board：每个发现都会命名修复调用（fixWith）。
概述（AI 翻译）
HeyPCB 用于 AI 代理。将 HeyPCB 添加到 Claude 代码、Codex、光标或 Claude 中
桌面和设计你的代理的真实KiCad板子：HeyPCB的服务器可以
工程部分（Inky的设计代理、零件、布置、布线、DRC/ERC，
FAB检查），你的代理人会调用一些高级工具，比如
build_board、get_board、check_board 和 export。或者你的代理人
他用HeyPCB的零件库和经过验证的电路块设计主板
并检查：search_parts、get_part、add_parts、add_block、connect，
get_netlist以及其他零件和电路工具，然后把它摆放好
与set_board_outline、set_board_rules、move_part、lock_parts，
add_ground_pour 和 get_board_layout，并通过
在 check_board] 之后：每个发现都指定了修复该问题的调用
（fixWith）。它看到它用preview_board（选择层，
高亮的网和部分，开连接），用
inspect_net、inspect_part 和 check_placement，表示各部分的位置与
set_placement_rules，控制铜，rip_up_net、add_pour，
add_keepout 和 stitch_vias，回顾了该板的历史
本页由 AI 翻译，技术细节请以原文为准。
README
以下为原文 README 节选，完整内容请查看原文。
@heypcb/mcp
HeyPCB for AI agents. Add HeyPCB to Claude Code, Codex, Cursor or Claude
Desktop and design real KiCad boards from your agent: HeyPCB’s server does
the engineering (Inky’s design agent, parts, placement, routing, DRC/ERC,
fab checks), and your agent calls a few high-level tools such as
build_board, get_board, check_board and export. Or your agent
designs the board itself with HeyPCB’s parts library, proven circuit blocks
and checks: search_parts, get_part, add_parts, add_block, connect,
get_netlist and the rest of the parts and circuit tools, then lays it out
with set_board_outline, set_board_rules, move_part, lock_parts,
add_ground_pour and get_board_layout, and takes it to fab-ready by
following check_board: every finding names the call that fixes it
(fixWith). It sees what it built with preview_board (chosen layers,
highlighted nets and parts, open connections), measures it with
inspect_net, inspect_part and check_placement, says where parts go with
set_placement_rules, controls copper with rip_up_net, add_pour,
add_keepout and stitch_vias, goes back through the board’s history with
list_history, restore_board and redo, and reads the playbook with
get_guide.
Two ways to design
| You say | Your agent calls | |
|---|---|---|
| Let HeyPCB design it | “Build a USB-C powered board for …” | build_board, get_board, check_board, export. HeyPCB’s server does the engineering: Inky’s design agent, parts, placement, routing, DRC/ERC and fab checks. |
| Let your agent design it | “Add an LDO and wire it to the MCU” | Parts and blocks: search_parts, get_part, add_parts, add_block, connect, get_netlist. Layout: set_board_outline, set_board_rules, move_part, lock_parts, add_ground_pour, get_board_layout. Then check_board until the board is fab-ready. Each finding names the call that fixes it (fixWith). |
Quick start
HeyPCB runs the MCP server for you at https://api.heypcb.ai/mcp (Streamable
HTTP, OAuth sign-in in your browser). Nothing to install:
claude mcp add --transport http heypcb https://api.heypcb.ai/mcp
claude.ai (as a custom connector) takes the same URL. Codex cannot sign in to the remote server (since codex-cli 0.165 it refuses an approve page on another origin than the issuer), so give Codex the local server below. One paste adds it and signs it in with a code:
codex mcp add heypcb -- npx -y @heypcb/mcp && npx -y @heypcb/mcp login
Which one do I need?
| Remote server | Local server (this package) | |
|---|---|---|
| Install | nothing | Node.js 18+ |
| All HeyPCB tools | ✅ | ✅ |
| Work on a KiCad project in its own folder, edits synced back | ❌ | ✅ open_kicad_project |
安装
npx -y @heypcb/mcp配置
{
"mcpServers": {
"heypcb": {
"command": "npx",
"args": ["-y", "@heypcb/mcp"]
}
}
}