PCB Forge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pcb_create_workspaceC | Create a project workspace using a safe project name. |
| pcb_generate_projectC | Generate a circuit project and run configured validation tools. |
| pcb_validate_projectC | Run configured KiCad ERC/DRC checks for an existing workspace. |
| pcb_export_manufacturingB | Export Gerber files after validation; human review is still required. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct stage of the PCB workflow (workspace creation, project generation, validation, export). There is mild overlap between pcb_generate_project (which also runs validation tools) and pcb_validate_project, but the descriptions clarify that one creates+validates while the other re-checks an existing workspace.
All tools share the pcb_ prefix and a consistent verb_noun pattern: create_workspace, generate_project, validate_project, export_manufacturing. The convention is uniform and predictable throughout.
Four tools map cleanly onto a single linear pipeline and each earns its place. The set is somewhat thin but well-scoped rather than padded or redundant.
The create→generate→validate→export lifecycle is covered, but there is no way to list or inspect existing workspaces, modify a project, or delete one. These are notable gaps that could force agents into dead ends when revisiting prior work.