Boardrepo MCP server
{
"mcpServers": {
"boardrepo": {
"type": "http",
"url": "https://boardrepo.com/mcp"
}
}
}{
"mcpServers": {
"boardrepo": {
"type": "http",
"url": "https://boardrepo.com/mcp"
}
}
}{
"mcpServers": {
"boardrepo": {
"type": "http",
"url": "https://boardrepo.com/mcp"
}
}
}{
"servers": {
"boardrepo": {
"type": "http",
"url": "https://boardrepo.com/mcp"
}
}
}{
"mcpServers": {
"boardrepo": {
"type": "http",
"url": "https://boardrepo.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.3.0
What it does
BoardRepo connects AI assistants to a library of real KiCad and Altium PCB designs for read-only access. Users can search public boards, inspect schematics and BOMs, run design checks, and review their own projects.
- Search and retrieve PCB board designs from a public repository to study schematic topology and component selection.
- Review bills of materials and netlists for boards you own to verify connectivity and component specifications.
- Run KiCad DRC/ERC checks and query design rules against fabrication profiles for boards in your account.
Tools this server exposes
| Tool | Does |
|---|---|
| public_board_search | Find publicly available PCB boards by design attributes and keywords. |
| board_metadata | Retrieve metadata about a board including design details and file information. |
| read_schematic | Access schematic connectivity and topology for a board. |
| read_bom | Retrieve the bill of materials for a board. |
| read_netlist | Retrieve the netlist for a board. |
| run_drc_erc | Execute KiCad design rule checks and electrical rule checks on a board. |
| query_design | Run structured queries against board design data. |
| get_fabrication_profile | Retrieve fabrication constraints and rules associated with a board. |
| review_board | Access design review data for boards you own or have authorization to review. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.