koppar
MCP server by Koppar · mcp
Koppar turns a circuit description into a manufacturable PCB. Through these tools YOU do the thinking (part research, writing the SKiDL schematic, reviewing it, planning the board) and Koppar does the deterministic work: KiCad library lookups, compiling and checking the circuit, place and route, the design-rule check, live BOM pricing and fab files. No model runs on the Koppar side. Workflow: 1. create_design with the user's brief. Give the user the web_url: the design, schematic, 3D board and BOM appear there as you work. 2. Research. Read get_workflow_guide(stage="research"). Verify every part with search_kicad_symbol, get_kicad_symbol and search_kicad_footprint, passing design_id so parts you register (create_custom_symbol, database parts) belong to the design. A package KiCad does not have: give create_custom_symbol its .kicad_mod as footprint_mod (or add_custom_footprint first, then footprint="custom:<name>") and the part uses that footprint on the board and in the project, neve…
Endpoint: https://app.koppar.ai/mcp
Verification: observed. Source: crawl.
Capabilities (68)
- get_workflow_guide
- create_design
- leave_feedback
- list_designs
- delete_design
- restore_design
- get_design
- search_kicad_symbol
- get_kicad_symbol
- search_kicad_footprint
- create_custom_symbol
- add_custom_footprint
- save_dossier
- submit_circuit
- edit_circuit
- read_design_file
- get_review_packet
- get_board_context
- start_board
- get_board_status
- get_bom
- choose_bom_part
- consolidate_bom_basic
- get_fab_status
- list_order_providers