# Koppar (remote · app.koppar.ai)

Design a KiCad PCB from a prompt: parts, schematic checks, routing, KiCad DRC and Gerbers.

- Trust score: 84/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `app.koppar.ai`: 84/100 (this document), [markdown](https://verifymcp.io/servers/ai-koppar-koppar/app.md), [page](https://verifymcp.io/servers/ai-koppar-koppar/app)

## Channel facts

- Endpoint: `https://app.koppar.ai/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 17820 tokens (~274/item across 65 items; 65 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability check failed: schema churn in the 18 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 6 additions.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 66 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Koppar MCP server?

Koppar is a hosted endpoint at https://app.koppar.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-koppar-koppar 'https://app.koppar.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-koppar-koppar": {
      "url": "https://app.koppar.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-koppar-koppar": {
      "type": "http",
      "url": "https://app.koppar.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-koppar-koppar]
url = "https://app.koppar.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-koppar-koppar": {
      "type": "remote",
      "url": "https://app.koppar.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-koppar-koppar --url 'https://app.koppar.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-koppar-koppar:
    url: "https://app.koppar.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-koppar-koppar": {
      "Transport": "http",
      "Url": "https://app.koppar.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-koppar-koppar -t streamable-http -u 'https://app.koppar.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-koppar-koppar": {
      "type": "http",
      "url": "https://app.koppar.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57.

### 2026-11-03 (score 83, +1)

- [functional] New tool “leave_feedback”
- [cosmetic] “create_design” added an optional parameter “new_project”
- [cosmetic] “create_design” added an optional parameter “session_id”
- [cosmetic] “import_kicad_project” added an optional parameter “new_project”
- [cosmetic] “import_kicad_project” added an optional parameter “session_id”

### 2026-11-01 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43.

### 2026-10-31 (score 81, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-30 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37.

### 2026-10-27 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27.

### 2026-10-26 (score 79, 0)

- [security regression] Stability: 0.23 → fail
- [security regression] A breaking change shipped without a version bump: still 0.1.0
- [security regression] Tool “board_census” was removed
- [security regression] Tool “score_board” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “prune_vias” rewrote its description, which is the text the model reads
- [cosmetic] “set_design_rules” reworded the description of “stackup”

### 2026-10-25 (score 79, 0)

- [cosmetic] “add_copper” reworded the description of “wait_s”
- [cosmetic] “anneal_place” reworded the description of “wait_s”
- [cosmetic] “auto_place” reworded the description of “wait_s”
- [cosmetic] “board_census” reworded the description of “wait_s”
- [cosmetic] “bridge_islands” reworded the description of “wait_s”
- [cosmetic] “check_net_rules” reworded the description of “wait_s”
- [cosmetic] “check_physics” reworded the description of “wait_s”
- [cosmetic] “cleanup_board” reworded the description of “wait_s”
- [cosmetic] “couple_pairs” reworded the description of “wait_s”
- [cosmetic] “diagnose_open_nets” reworded the description of “wait_s”
- [cosmetic] “export_step” reworded the description of “wait_s”
- [cosmetic] “fill_zones” reworded the description of “wait_s”
- [cosmetic] “finish_board” reworded the description of “wait_s”
- [cosmetic] “get_board_info” reworded the description of “wait_s”
- [cosmetic] “get_board_job” reworded the description of “wait_s”
- [cosmetic] “place_footprints” reworded the description of “wait_s”
- [cosmetic] “polish_vias” reworded the description of “wait_s”
- [cosmetic] “prune_vias” reworded the description of “wait_s”
- [cosmetic] “render_board” reworded the description of “wait_s”
- [cosmetic] “repair_board” reworded the description of “wait_s”
- [cosmetic] “restore_board_revision” reworded the description of “wait_s”
- [cosmetic] “ripup_routing” reworded the description of “wait_s”
- [cosmetic] “route_board” reworded the description of “wait_s”
- [cosmetic] “run_drc” reworded the description of “wait_s”
- [cosmetic] “score_board” reworded the description of “wait_s”
- [cosmetic] “set_board_outline” reworded the description of “wait_s”
- [cosmetic] “set_design_rules” reworded the description of “wait_s”
- [cosmetic] “set_keepouts” reworded the description of “wait_s”
- [cosmetic] “set_silkscreen” reworded the description of “wait_s”
- [cosmetic] “set_zones” reworded the description of “wait_s”
- [cosmetic] “stamp_silkscreen” reworded the description of “wait_s”
- [cosmetic] “swap_footprint” reworded the description of “wait_s”
- [cosmetic] “tidy_copper” reworded the description of “wait_s”
- [cosmetic] “tie_rail_pads” reworded the description of “wait_s”
- [cosmetic] “widen_nets” reworded the description of “wait_s”

## MCP tools (65)

### `get_workflow_guide` (~92 tokens)

Workflow guide

How to drive Koppar end to end, and the instructions for each stage you do yourself: "research" (part research and the dossier), "synthesis" (writing the SKiDL schematic), "review" (design review), "board" (the board plan). Read the stage guide before doing that stage.

Input parameters:

- `stage` (string, required): overview | research | synthesis | review | board

### `create_design` (~163 tokens)

Create a design

Start a new design from the user's brief (what the board must do, its interfaces, power, size and constraints). Returns the design_id every other tool takes and the web_url where the user follows the design. Uses no generation quota: the work is done by you.

Input parameters:

- `brief` (string, required): The design brief, in the user's terms plus anything you clarified with them.
- `new_project` (boolean): Start a new project even when one with this title exists.
- `session_id` (string): The project (web session) to put this design in: the session_id an earlier design of this board returned. Without it, a design whose title matches a project you opened before joins that project.
- `title` (string): A short name for the design.

### `leave_feedback` (~151 tokens)

Leave feedback

Send the Koppar team feedback from the user: about Koppar in general, or about one design (design_id). A rating from 1 to 5, a message, or both. Use it when the user asks you to pass something on, or tells you what worked or did not; say in the message what happened, in their words where you can. The team reads every one.

Input parameters:

- `design_id` (string): The design it is about, when it is about one.
- `message` (string): What the user wants us to know, in their words where you can.
- `rating` (integer): 1 (poor) to 5 (great), when the user gave one.

### `list_designs` (~90 tokens)

List designs

The user's designs, newest first, including ones made in the web app (an agent can continue those too) and board workspaces (kind "board workspace"). With trashed, the designs in the trash instead (deleted, restorable for 7 days).

Input parameters:

- `limit` (integer): How many (default 20).
- `trashed` (boolean): List the trash instead of the live designs.

### `delete_design` (~123 tokens)

Delete a design

Move a design (or a board workspace) to the trash: it leaves list_designs and the web app, and restore_design brings it back for 7 days, after which it is removed for good. permanent removes it, its files and its session right away. Refused while a run on it is in progress. The CLI: `koppar delete <design>`.

Input parameters:

- `design_id` (string, required): The design id returned by create_design or list_designs.
- `permanent` (boolean): Remove it now, with no trash to restore from (default false).

### `restore_design` (~44 tokens)

Restore a design from the trash

Put a deleted design back from the trash (within 7 days of delete_design).

Input parameters:

- `design_id` (string, required): The design id returned by create_design or list_designs.

### `get_design` (~67 tokens)

Design status

Where a design stands: the brief, the schematic (accepted or the last blocking error, ERC, part and net counts, submissions), the board run, the readable files, and the next step.

Input parameters:

- `design_id` (string, required): The design id returned by create_design or list_designs.

### `search_kicad_symbol` (~203 tokens)

Search KiCad symbols

Search KiCad's standard symbol libraries for parts whose name contains a substring. Use this whenever you are not 100% sure the (library, name) pair you're about to pass to Part(...) exists. Always prefer the package-suffixed variant the search returns over a generic name. If a part returns nothing here, get_kicad_symbol(library='custom', name='<part number>') may find it in the component database (a datasheet link and a pinout lead); register it with create_custom_symbol. Pass design_id so the lookup is recorded for the design's dossier and a registered part belongs to it.

Input parameters:

- `design_id` (string): The design id returned by create_design or list_designs.
- `library` (string): Restrict to one symbol library, e.g. 'Timer'.
- `query` (string, required): Substring to search for, e.g. 'NE555', 'USB-C', 'RP2040'.

### `get_kicad_symbol` (~309 tokens)

Get a KiCad symbol

Return the full pin list (number, name, electrical type) and description for a specific KiCad symbol. For some high-risk power parts it also returns curated topology_constraints from datasheet-style application notes and footprint_suggestions. Use this before writing pin connections (e.g. mcu['VCC'] += vcc) so names, constraints and footprints match the symbol exactly. For a part found in KiCad, the result is ALSO enriched with that part's topology + required external parts from a datasheet database (merged into topology_constraints). For a part NOT in KiCad (search returned nothing), call this with library='custom' and name='<part number>': the component database returns its datasheet link, package and an UNVERIFIED machine-extracted pinout. That is not a symbol: register the part with create_custom_symbol, whose pinout is checked against the datasheet. Pass design_id so the lookup is recorded for the design's dossier and a registered part belongs to it. Give library and name, or up to 12 of them in parts.

Input parameters:

- `design_id` (string): The design id returned by create_design or list_designs.
- `library` (string): Symbol library, e.g. 'MCU_RaspberryPi', or 'custom' for a database part number.
- `name` (string): Symbol name, e.g. 'RP2040'.
- `parts` (array): Batch form: several (library, name) pairs.

### `search_kicad_footprint` (~173 tokens)

Search KiCad footprints

Search KiCad's standard footprint libraries. Returns 'Library:Footprint' strings suitable for the footprint= argument of Part(...). Query with the package family and pin count ('LGA-14', 'QFN-24', 'SOIC-8'), optionally a body size or pitch. When no name contains every word, near_misses lists footprints of the same package, ranked by body size and pitch. Pass design_id so the lookup is recorded for the design's dossier and a registered part belongs to it.

Input parameters:

- `design_id` (string): The design id returned by create_design or list_designs.
- `query` (string, required): Package to search for, e.g. 'SOIC-8', 'QFN-56 7x7', 'USB_C_Receptacle'.

### `create_custom_symbol` (~506 tokens)

Register a custom symbol

Register a connectable schematic symbol for a part that is NOT in KiCad's libraries (search_kicad_symbol returned nothing). Use this for specialty ICs — LED-matrix drivers, niche sensors, etc. — INSTEAD of telling the synthesizer to model the part with discrete passives (which leaves every pin dangling and breaks the board). Provide the full datasheet pinout. The part then becomes available to the synthesizer as Part('custom', '<name>') with the exact pin names you supply here, and is added to the Verified parts table. A part with three or more pins needs footprint= naming a real, in-library footprint for its package (search_kicad_footprint with the family and pin count, e.g. 'LGA-14'); the call is rejected without one, since a generated grid of pads cannot be assembled. List every pad of the footprint, NC pins included. When the package is not in KiCad's libraries, bring your own footprint instead: footprint_mod takes the whole .kicad_mod file as text (KiCad 6+, up to 1 MB; the CLI reads it with `koppar custom-symbol --footprint-file`). It is checked as a KiCad footprint, every pad must have a pin with that pad's number (and every pin a pad), and it is stored as 'custom:<name>': the symbol uses it, and it goes on the board, into project.zip and into the fp-lib-table. footprint is then not needed. The name is used for file names: letters, digits and _ . + - (anything else becomes _). The symbol belongs to design_id.

Input parameters:

- `datasheet` (string)
- `description` (string)
- `design_id` (string, required): The design id returned by create_design or list_designs.
- `footprint` (string): A 'Library:Footprint' from search_kicad_footprint. Required for 3+ pins unless footprint_mod is given.
- `footprint_mod` (string): Your own footprint: the full text of a .kicad_mod file, starting with '(footprint'. Its pad numbers must match the pin numbers.
- `name` (string, required): Part number, used as the symbol name (letters, digits, _ . + -).
- `pins` (array, required): Every pin from the datasheet.
- `reference` (string): Reference prefix, e.g. 'U'.

### `add_custom_footprint` (~187 tokens)

Add your own footprint

Give the design a footprint of your own: a KiCad .kicad_mod (the file's text) for a package KiCad's libraries lack. It joins the design's "custom" footprint library and is used as "custom:<name>": pass that to create_custom_symbol (footprint=) or name it in the SKiDL script's footprint=; the board builder loads it like a library footprint and the KiCad project download carries it. The pads must be numbered like the pins. The CLI: `koppar footprint <design> part.kicad_mod`.

Input parameters:

- `design_id` (string, required): The design id returned by create_design or list_designs.
- `kicad_mod` (string, required): The .kicad_mod file, as text.
- `name` (string): The footprint name (default: the name inside the file).

### `save_dossier` (~118 tokens)

Save the parts dossier

Store the research dossier (markdown with ## Parts list, ## Power rails, ## Topology constraints, ## Notes, as the research guide describes). The verified pin tables from your lookups on this design are appended, and verified entries the design already had for parts you did not look up again are kept. Reports every (library, name) in the parts list that does not exist, with catalog candidates.

Input parameters:

- `design_id` (string, required): The design id returned by create_design or list_designs.
- `markdown` (string, required): The dossier.

### `submit_circuit` (~162 tokens)

Submit the schematic

Compile and check a complete SKiDL script: the symbol and footprint pre-flight (unambiguous typos are corrected and listed), SKiDL, the ERC score, KiCad ERC, floating subsystems, parts without a footprint, and supplier sourcing. Returns accepted plus blocking findings to fix and warnings. An accepted script becomes the design's circuit.py; one that is sent back is kept as attempt_N_circuit.py and leaves the design as it was. Takes up to a couple of minutes.

Input parameters:

- `check_sourcing` (boolean): Check the parts against supplier catalogues (default true).
- `code` (string, required): The complete SKiDL Python script.
- `design_id` (string, required): The design id returned by create_design or list_designs.

### `edit_circuit` (~133 tokens)

Patch the schematic

Apply SEARCH/REPLACE patches to your latest script and re-run every check, as submit_circuit does. The latest script is your last submission when it was sent back (attempt_N_circuit.py), otherwise the design's circuit.py. Each search must match the current file exactly once (whitespace-sensitive); an empty replace deletes. Nothing is applied if any block fails to match.

Input parameters:

- `check_sourcing` (boolean): Check the parts against supplier catalogues (default true).
- `design_id` (string, required): The design id returned by create_design or list_designs.
- `edits` (array, required): Ordered patches.

### `read_design_file` (~127 tokens)

Read a design file

Read a text file of the design: prompt.txt (brief), dossier.md, circuit.py, circuit.net, result.json, circuit.erc.json (KiCad ERC violations), attempt_N_circuit.py / attempt_N_error.txt, board_plan.json, pcb_result.json, pcb_run.log, circuit.drc.json (KiCad DRC), netclasses.resolved.json, dfm.json, harness.log.

Input parameters:

- `design_id` (string, required): The design id returned by create_design or list_designs.
- `path` (string, required): A file name, e.g. 'circuit.py'.

### `get_review_packet` (~75 tokens)

Design review packet

Everything a design review needs in one text: the brief, the dossier, circuit.py and the compiled connectivity (every net with every pin and its function), with the reviewer instructions. Review it yourself and fix blockers with edit_circuit.

Input parameters:

- `design_id` (string, required): The design id returned by create_design or list_designs.

### `get_board_context` (~80 tokens)

Board planning context

What the board plan is decided from: the computed minimum board, BOARD STATS (pad density, fine-pitch parts, fanout), the parts and nets, board instructions the user gave, and the plan schema with its rules. Needs an accepted schematic.

Input parameters:

- `design_id` (string, required): The design id returned by create_design or list_designs.

### `start_board` (~122 tokens)

Place and route the board

Start place and route with your board plan (the JSON object from the board guide: board, stated, edge, chain, groups, near, side, fixed, keepouts, netClasses). The plan is clamped and returned as applied. Runs for minutes in the background: follow it with get_board_status. Needs an accepted schematic; one board run per design at a time.

Input parameters:

- `design_id` (string, required): The design id returned by create_design or list_designs.
- `plan` (object): The board plan object. Omit for the default plan.

### `get_board_status` (~133 tokens)

Board status

The board run: stage, size, layers, placement, routing completion, open nets, DRC counts; once finished, DRC violations by type, whether the fab files are released and, when not, the diagnosed causes (first = fix first: parts that did not fit, collisions, missing footprints, open nets, thin power). wait_s holds the call until the run ends (or that many seconds pass).

Input parameters:

- `design_id` (string, required): The design id returned by create_design or list_designs.
- `wait_s` (integer): Seconds to wait for a running board to finish (max 55).

### `get_bom` (~164 tokens)

Bill of materials

The live-priced BOM: each line with references, value, footprint, the chosen offer (seller, part number, MPN, price, stock, match quality), alternatives and totals. refresh asks the sellers again (tens of seconds).

Input parameters:

- `boards` (integer): Boards to price for (default 1).
- `design_id` (string, required): The design id returned by create_design or list_designs.
- `refresh` (boolean): Ask the sellers again instead of the stored prices.
- `tier` (string): JLCPCB PCBA tier to source for, kept with the design. 'economic' swaps Standard-only parts for Economic-eligible ones that match as well; default 'standard' (no filter). The BOM reports which parts d…

### `choose_bom_part` (~119 tokens)

Choose a BOM offer

Pick which offer a BOM line uses: the line's references and a seller part number or MPN from its offer or alternatives in get_bom; null goes back to the automatic pick. Sourcing only: a different component is a circuit change.

Input parameters:

- `design_id` (string, required): The design id returned by create_design or list_designs.
- `part` (required): Seller part number or MPN from get_bom, or null.
- `refs` (array, required): References of the line, e.g. ["C1","C2"].

### `consolidate_bom_basic` (~146 tokens)

Consolidate the BOM to JLCPCB basic parts

Move every resistor, capacitor and inductor bought outside JLCPCB's basic library onto an in-stock basic-library part of the same value, package and (capacitors) at least the same voltage rating. Each part outside that library adds a loading fee to a JLCPCB order, usually more than the part. Each swap becomes the line's choice (choose_bom_part with null undoes it); lines with no readable value, no SMD size or no basic part are reported and left alone.

Input parameters:

- `boards` (integer): Boards the stock must cover (default 1).
- `design_id` (string, required): The design id returned by create_design or list_designs.

### `get_fab_status` (~55 tokens)

Fab release status

Whether the board has earned its fab files (zero serious DRC errors, nothing unconnected), and if not, why not.

Input parameters:

- `design_id` (string, required): The design id returned by create_design or list_designs.

### `list_order_providers` (~36 tokens)

Manufacturers

The PCB and assembly providers, whether each can quote and take this kind of board today, and what a handoff sends them.

### `get_order_price` (~95 tokens)

Order price

One price for a quantity: parts from the sellers, the board and assembly from the chosen provider's quote, setup fees, and what the total does not include.

Input parameters:

- `boards` (integer): Quantity (default 1).
- `design_id` (string, required): The design id returned by create_design or list_designs.
- `provider` (string): Provider id from list_order_providers, e.g. "jlcpcb".

### `send_order_to_provider` (~165 tokens)

Send the order to a manufacturer

Upload the released board (Gerbers, BOM, placement) to a manufacturer and return the page where the user pays. This publishes the design to a third party: call it only when the user has explicitly asked to order from that provider, and set user_confirmed only then. Some providers need a shipping address.

Input parameters:

- `boards` (integer): Quantity (default 1).
- `design_id` (string, required): The design id returned by create_design or list_designs.
- `provider` (string, required): Provider id from list_order_providers.
- `shipping` (object): Delivery address, for providers that need one.
- `title` (string): Order title at the provider.
- `user_confirmed` (boolean, required): The user explicitly asked to send this design to this provider.

### `upload_board` (~321 tokens)

Upload a board

Replace the design's board with a .kicad_pcb you routed or edited yourself (the file, base64). The board must carry the design's circuit: every schematic part by reference, every pad on the net the netlist gives it; a footprint swap is allowed and recorded. Anything else is refused with the list of differences and nothing changes. The previous board is kept as circuit.before-upload.kicad_pcb. KiCad DRC judges the new board and releases or withholds the Gerbers, and the session chat gets a note of the upload. Not for a board workspace (import_kicad_project): its board tools edit the board in place.

Input parameters:

- `board_base64` (string): The .kicad_pcb file, base64 (or give workspace_id).
- `design_id` (string, required): The design id returned by create_design or list_designs.
- `note` (string): What was done to the board, for the session chat.
- `project_base64` (string): The .kicad_pro beside the board, base64: its design rules and net classes judge the board (without it the design keeps its own).
- `rules_base64` (string): The .kicad_dru beside the board, base64.
- `workspace_id` (string): A board workspace of yours (import_kicad_project, e.g. one made from this design with from_design_id): its board, project rules and .kicad_dru are taken from there, no download and upload.

### `get_downloads` (~94 tokens)

Downloads

Download URLs for the design (KiCad project, schematic, netlist, BOM CSV, board file, 3D model, Gerbers, order bundle) and which are available now. They take the same Authorization: Bearer API key; the CLI fetches them with `koppar download <design> <artifact>`.

Input parameters:

- `design_id` (string, required): The design id returned by create_design or list_designs.

### `import_kicad_project` (~337 tokens)

Import a KiCad project

Bring an existing KiCad project in as a board workspace: the project folder as a ZIP (the .kicad_pcb, .kicad_pro, schematics, footprint and 3D-model folders), base64-encoded, up to about 18 MB zipped. The CLI does this with `koppar import <folder>`. Or from_design_id: the KiCad project of a design the pipeline built (its board, rules, schematics and custom footprints) opened as a workspace, to change the design rules, place and route it with the board tools and put the result back with upload_board (workspace_id). Returns the design_id the board tools take and a first get_board_info.

Input parameters:

- `board_file` (string): Which .kicad_pcb at the top of the project, when there are several.
- `brief` (string): What the user wants done with the board, for the design record.
- `from_design_id` (string): A design of yours with a board (start_board or upload_board): its KiCad project becomes the workspace. Instead of zip_base64.
- `new_project` (boolean): Start a new project even when one with this title exists.
- `session_id` (string): The project (web session) a new revision of this board goes into: the session_id the first import returned. Without it, an import whose title matches a project you opened before joins that project, s…
- `title` (string)
- `zip_base64` (string): The zipped project folder, base64.

### `get_board_info` (~216 tokens)

Board info

The board as it stands: copper layers, outline, design rules and net classes, counts (footprints, nets, tracks, vias, zones, keepouts, KiCad unconnected items), zones and keepouts, and every footprint with reference, value, footprint, position (origin, mm), rotation, side, locked, DNP, courtyard box and 3D models.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `include_footprints` (boolean): List footprints (default true).
- `refs` (array): Only these footprints.
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `place_footprints` (~208 tokens)

Place footprints exactly

Put footprints exactly where given: KiCad board coordinates of the footprint origin in mm (y grows downward), rotation in degrees as KiCad shows it, side F or B (changing side flips the footprint, as KiCad does), locked. dx_mm/dy_mm/drot_deg move relative to where it is. Nothing is nudged or legalized: overlaps are for run_drc to report. Unknown references come back in missing.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `placements` (array, required)
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `auto_place` (~887 tokens)

Auto-place footprints

Pack footprints inside the board outline with Koppar's heuristic placer (ratsnest-driven, courtyard-legal). By default every unlocked footprint moves and locked ones stay; refs names exactly which move (all others stay). Constraints: fixed (exact origin positions and rotation, never moved; locked footprints likewise), side, keepouts (rectangles), groups, near (ref within maxMm of an anchor), edge (ref to "left|right|top|bottom", optionally "@mm" along that edge from the outline's top-left corner). Nothing is left past the outline except a USB/barrel/jack opening's 1.2 mm lip; placement_notes lists every part that could not be placed where asked. Coarse by design: refine the result with place_footprints.

Input parameters:

- `bottom_any` (boolean): Refine: any SMD-only part may go to the back, priced by flip_cost (default with two_sided); LEDs, switches, displays and test points stay on top.
- `bottom_exclude` (string): Refine: regex of refs or footprint ids that stay on top.
- `bottom_max_height_mm` (number): Refine: tallest part allowed on the back (3D-model height, default 1.0).
- `bottom_ok` (array): Refine: footprint-id substrings allowed on the back instead of bottom_any.
- `connector_flank_mm` (number): Refine: room kept on the flanks of every edge connector (default 1.0); sets the pitch of connectors sharing an edge.
- `connector_room_mm` (number): Refine: room kept on the board side of every edge connector (default 2.5).
- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `edge` (object): Ref to the edge it sits on, optionally @mm: where along that edge its centre goes, from the outline's top-left corner (x on top/bottom, y on left/right).
- `fixed` (object)
- `flip_cost` (number): Annealing price per bottom-side pad whose net has top pins (default 3).
- `grid_mm` (number): Placement grid for the refine step (0.254 = 10 mil); default off.
- `groups` (array)
- `hole_room_mm` (number): Refine: room kept around mounting holes, both sides (default 1).
- `ic_halo_mm` (number): Refine: room kept around ICs with 48+ pads (default 1.5; 16+ pads and fine pitch get two thirds).
- `iterations` (integer): Annealing iterations for refine (default 600000).
- `keepouts` (array)
- `near` (array)
- `overlap_weight` (number): Overlap price per mm2 at the end of the anneal (default 400; 4000 halves what a dense draw leaves).
- `placer` (string): "ml": the learned placer service (dense, two-sided when two_sided, honours keepouts); the packer when it is unavailable.
- `refine` (string): "anneal": refine the placement by simulated annealing from this seed (wirelength-driven, same edge/fixed/keepouts, holes held) — the ML placer's structure with the annealer's tightness.
- `refs` (array): The footprints that may move.
- `shove` (number): Legaliser: a part may take a spot held only by movable parts under this fraction of its area (default 0.3, 0 off).
- `side` (object)
- `split_cost` (number): Refine: price (mm of wirelength) of an SMD net with pads on both sides, i.e. a via.
- `two_sided` (boolean): Small two-pad passives go to the back side.
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `anneal_place` (~981 tokens)

Anneal a dense placement

Dense placement by simulated annealing: wirelength inside the outline with courtyard gaps, edge connectors held on their edge, fixed and locked parts held, keepout rectangles kept clear (routing corridors), and a per-pad price for the bottom side (flip_cost, mm of wirelength; each bottom-side pad whose net has top-side pins costs a via). Starts from the current positions unless from_scratch. Slower than auto_place (a minute per 600k iterations) and much denser. Check overlapping_pairs and run_drc afterwards.

Input parameters:

- `bottom_any` (boolean): Any SMD-only part may go to the back (priced by flip_cost); LEDs, switches, displays and test points stay on top unless bottom_exclude says otherwise.
- `bottom_exclude` (string): Regex of refs or footprint ids that stay on top regardless.
- `bottom_max_height_mm` (number): Tallest part allowed on the back (3D-model height, default 1.0): the assembly box grows by the tallest back-side part.
- `bottom_ok` (array): Footprint-id substrings allowed on the bottom side (e.g. "0402").
- `connector_flank_mm` (number): Room kept on the flanks of every edge connector (default 1.0).
- `connector_room_mm` (number): Room kept on the board side of every edge connector (default 2.5).
- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `edge` (object): Connector ref to the edge it sits on, optionally @mm: where along that edge its centre goes, from the outline's top-left corner (x on top/bottom, y on left/right) — the same meaning as in auto_place…
- `edge_overhang_mm` (object): Per edge ref, how far its body sits past the edge: default 0.5 for a USB/barrel/jack connector (at most its 1.2 mm lip), 0 (flush) for anything else, which may not overhang.
- `fixed` (object): Parts held at these origin positions; they are moved there on the board first.
- `flip_cost` (number)
- `from_scratch` (boolean)
- `gap_mm` (number)
- `grid_mm` (number): Placement grid for free parts (0.254 = 10 mil, the designer habit); default off.
- `halo` (object): Routing room per ref, mm (a number all round, or footprint-local [left, top, right, bottom]).
- `hole_room_mm` (number): Room kept around mounting holes on both sides for the screw head and standoff (default 1).
- `ic_halo_mm` (number): Room kept around ICs with 48+ pads (default 1.5).
- `iterations` (integer)
- `keepouts` (array): Rectangles no part may cover, e.g. a bus corridor.
- `near` (array): Keep ref at its anchor (a decoupling capacitor at its IC, a crystal at its MCU): the board plan's near constraint, as a strong pull in the anneal.
- `net_weight` (object)
- `overlap_weight` (number): Overlap price per mm2 at the end of the anneal (default 400; 4000 halves what a dense draw leaves).
- `refit_from` (object): Outline the current placement was drawn in; it is scaled affinely into the new outline before annealing (with t0 ~0.5: shrink a placement that closed).
- `refs` (array): The footprints that may move (default: every unlocked one).
- `rotations` (array)
- `seed` (integer)
- `shove` (number): Legaliser: a part may take a spot held only by movable parts under this fraction of its area (default 0.3, 0 off).
- `split_cost` (number): Price (mm of wirelength) of an SMD net with pads on both sides, i.e. a via.
- `t0` (number): Start temperature (default 15). ~0.5 keeps the current placement and only tidies it (refine, or squeeze into a smaller outline).
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `set_board_outline` (~190 tokens)

Set the board outline

Replace everything on Edge.Cuts with a new outline: rect (optionally with corner_radius_mm), a polygon of points, or fit_to_parts (the rectangle around every footprint courtyard plus margin_mm). Give exactly one.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `fit_to_parts` (object)
- `line_width_mm` (number)
- `polygon` (array)
- `rect` (object)
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `set_design_rules` (~776 tokens)

Set design rules

Set the project design rules (.kicad_pro) and copper layer count. Works on a board workspace and on a generated design (create_design → start_board). On a generated design the rules go into circuit.kicad_pro/.kicad_dru in place (the previous ones are snapshotted under rules_revisions/), are kept by every later project write (project.zip, a new board run), the copper is not changed and KiCad DRC judges the board against them at once: the reply carries the DRC counts and whether the Gerbers are released; the next start_board routes to the default_* values. copper_layers, stackup and board_thickness_mm are workspace-only (a generated design changes them with a new board). preset "jlcpcb" applies JLCPCB's published minimums for the layer count and writes their per-feature limits (plated rings, pad hole spacing, hole-to-track) as KiCad custom rules (.kicad_dru) that run_drc checks; explicit values override the minimums. Board minimums (min_*), the Default net class (default_*), and named net classes with their net patterns. route_board routes with these rules and run_drc checks against them. Changing copper_layers rebuilds the stackup; tracks on removed layers are reported. copper_layers 1 is a single-sided board (hand etching): the KiCad file keeps F.Cu and B.Cu, and from then on the routers hold to one face (B.Cu as soon as a THT pad exists, else F.Cu) and place no via; copper on the other face is removed.

Input parameters:

- `board_thickness_mm` (number): Finished board thickness; the stackup is rebuilt to it. JLCPCB FR4: 0.4, 0.6, 0.8, 1.0, 1.2, 1.6, 2.0 mm.
- `copper_edge_clearance_mm` (number)
- `copper_layers`
- `default_clearance_mm` (number)
- `default_track_mm` (number)
- `default_via_diameter_mm` (number)
- `default_via_drill_mm` (number)
- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `hole_clearance_mm` (number)
- `hole_to_hole_mm` (number)
- `min_clearance_mm` (number)
- `min_through_drill_mm` (number)
- `min_track_mm` (number)
- `min_via_annular_mm` (number)
- `min_via_diameter_mm` (number)
- `net_classes` (array)
- `preset` (string)
- `stackup` (string): 1.6 mm impedance stackups, written into the board: JLCPCB's 4-layer 7628 (0.21 mm prepreg, their default) or 3313 (0.1 mm prepreg: thinner pairs for the same impedance), and 6- / 8-layer 3313 builds…
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `set_keepouts` (~212 tokens)

Keepout areas

Add or remove keepout rule areas. Each keepout is a rect or polygon on the given copper layers (default all) and forbids what it names: no_tracks, no_vias, no_zone_fills (all three default true), no_pads, no_footprints. route_board keeps tracks and vias out of them and KiCad DRC enforces them. remove takes names (wildcards allowed).

Input parameters:

- `add` (array)
- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `remove` (array)
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `check_net_rules` (~195 tokens)

Check net classes and pairs

Check the copper against the project's net classes and differential pairs, which KiCad's DRC does not: every class or pair net's narrowest track and the length below its class width, and every pair (X_P/X_N, X+/X-, CAN X_H/X_L) with its coupled share at the class's diff_pair_gap, both lengths and the skew. Routing applies the same rules.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `check_physics` (~244 tokens)

Check the physics

Judge the copper by physics, which KiCad's DRC does not: impedance from the stackup on controlled nets, IR drop and heating on rails with a stated current, pair and lane skew, a ground via beside every high-speed layer change, 3W spacing between high-speed runs, and the via path under exposed paddles. Each check runs only when the board states something it can judge. With repair, the fixable findings are fixed in place (track width, skew meanders, return vias, widened rails), each kept only if KiCad counts nothing worse. finish_board runs the same repairs.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `repair` (boolean)
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `set_zones` (~214 tokens)

Copper zones

Add or remove copper zones (pours). Each zone pours its net on the given copper layers over rect or polygon, by default the whole board outline. priority orders overlapping zones (higher fills first); clearance_mm and min_thickness_mm override the rules; thermal false connects pads solid. remove takes zone or net names (wildcards allowed) and never touches keepout areas. Run fill_zones afterwards, then run_drc.

Input parameters:

- `add` (array)
- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `remove` (array)
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `add_copper` (~200 tokens)

Add tracks and vias

Lay exact copper by hand where the routers leave a gap: tracks as polylines on one copper layer, and through vias. width_mm, diameter_mm and drill_mm default to the board's current track and via sizes. Nets must exist on the board. Nothing is checked here: run_drc afterwards, and ripup_routing takes copper back out.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `tracks` (array)
- `vias` (array)
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `prune_vias` (~207 tokens)

Remove redundant vias

Remove every via the board does not need: groups of vias come out, the zones are refilled and KiCad's unconnected count compared, and a via stays only if removing it disconnects something. nets limits the candidates (GND and the plane rails first: pours already join most of their pads). Runs for minutes on a large board; then fill_zones, run_drc.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `nets` (array)
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…
- `workers` (integer)

### `set_silkscreen` (~211 tokens)

Tidy the silkscreen

Take clutter off the silkscreen. values "hide" (default) hides value and part-number fields; references "keep" (default), "fab" (moved to the fabrication layer) or "hide"; texts "fab" moves footprint texts off the silkscreen. run_drc's silk_overlap and silk_over_copper warnings count what is left.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `references` (string)
- `texts` (string)
- `values` (string)
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `route_board` (~1591 tokens)

Route the board

Route under the project's rules and net classes. By default (no nets, no router, none of the single-route options below) it runs the full route pipeline Koppar benchmarks: the learned router on the whole board racing the negotiated router on a copy (the board with fewer open items, then fewer DRC errors, goes on), repair rounds on what stays open, the local finish, copper finishing (0/45/90 runs) and one repair round after it, inside one wall-clock cap: time_budget_s is that cap (default 1200, up to 1500), so the job runs up to about 20 minutes: follow it with get_board_job. The result gives the final unconnected items and DRC errors and a pipeline summary: the counts after the route and after each finish, which arm won, whether the copper finishing was kept. preserve_existing unset keeps the copper of a board that has tracks or vias (the negotiated arm then does not run: it routes from scratch) and routes a board without any from scratch; false routes every net again. nets, router, or any single-route option (pours, rule overrides, via_cost, grid_mm, negotiation_rounds, ml_options, seed_existing, fewest_vias, pairs_first, class_vias) runs ONE route with that router instead, for expert control: nets limits it to those nets; preserve_existing (default true) keeps every track and via already on the board and routes only what is still open. pours: "keep" (the default when the board has zones) keeps the board's zones and routes every net as tracks; "engine" plans a GND pour and fans GND to it by via. Rule overrides apply to this run only. via_cost raises the price of a via in the local router (its default is 2), for fewer vias at some completion cost; the learned router takes its via discipline in ml_options. A single route takes time_budget_s (default 120, up to 900).

Input parameters:

- `class_vias` (boolean): Route with the Default class's via. Without it (and without via_diameter_mm) a route uses the board's smallest legal via where the class's is larger.
- `clearance_mm` (number)
- `compact` (boolean): true: the densest via the rules allow (0.4/0.2), which JLCPCB prices with a mandatory 4-wire Kelvin test (~$40 per order); false: never below the Kelvin-free 0.45/0.2. Unset: compact only on a board…
- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `edge_clearance_mm` (number)
- `fewest_vias` (boolean): Router "negotiated": the fine-grid router alone with its via phase (every net rerouted at 3x the via price and settled again): fewer vias, 2-3x the time.
- `grid_mm` (number)
- `ml_options` (object): Fields passed to the learned router service as they are (router "ml"): via_cost and via_cost_hi (prices in lattice cells; a move costs 1 and the served default via is 8, 12 while a net is on the qual…
- `negotiation_rounds` (integer)
- `nets` (array): Net names; * and ? wildcards, e.g. ["USB_D*", "+3V3"].
- `pairs_first` (boolean): Route the differential pairs (USB D+/D-, CAN H/L, X_P/X_N) alone first, then everything else around them: a port pad row only lets a pair out before the neighbours take its lane.
- `pours` (string)
- `preserve_existing` (boolean)
- `router` (string): Unset: the full pipeline (above) on the whole board, "ml" for nets. "ml": the learned router service alone, 1 to 8 layers; the time budget is its deadline. Nets outside the nets scope, and with prese…
- `seed_existing` (boolean): ML router: the connected nets in scope are sent as their own routes (seed_copper) and the service reworks the finished board with its rip-up and via-economy passes; kept only when KiCad counts fewer…
- `time_budget_s` (integer): The full pipeline's wall-clock cap (default 1200), or a single route's budget (default 120, up to 900).
- `track_width_mm` (number)
- `via_cost` (number)
- `via_diameter_mm` (number)
- `via_drill_mm` (number)
- `vias_in_pads` (string): 'forbid' (default): no via inside an SMD pad under 2 mm. 'allow': vias may sit in pin pads, for a board ordered with filled and capped vias (JLCPCB POFV); dense connector rows close that otherwise st…
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `repair_board` (~270 tokens)

Repair open connections

Keep the copper of every net it already connects and route the nets still open around it: route_board with preserve_existing. The learned router service by default; router "ts" for the local router, which also keeps partial copper and runs its last-chance welds and plane-island bridges. Default budget 120 s.

Input parameters:

- `compact` (boolean): Via choice as on route_board: true for the densest legal via (JLCPCB Kelvin test), false for the Kelvin-free 0.45/0.2.
- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `nets` (array): Net names; * and ? wildcards, e.g. ["USB_D*", "+3V3"].
- `pours` (string)
- `router` (string)
- `time_budget_s` (integer)
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `ripup_routing` (~270 tokens)

Rip up routing

Delete tracks and vias: of the given nets, on the given layers (vias are not layer-filtered), with an end inside region, or all. Filters combine. tracks/vias choose which kinds (both by default); zones also deletes the copper zones (pours) the same filters match (a zone inside region), never keepout areas. Locked items stay unless include_locked.

Input parameters:

- `all` (boolean)
- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `include_locked` (boolean)
- `layers` (array)
- `nets` (array): Net names; * and ? wildcards, e.g. ["USB_D*", "+3V3"].
- `region` (object)
- `tracks` (boolean)
- `vias` (boolean)
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…
- `zones` (boolean)

### `cleanup_board` (~273 tokens)

Clean up tracks and vias

Sweep the routing: zero-length and duplicate tracks, stub tracks (a free end, and everything the track touches stays joined without it), and vias that meet their net on fewer than two layers. Contact is copper overlap, as KiCad judges it. Refills the zones first so pours count as connections. Locked items stay. The board is put back if the unconnected count or the DRC errors rise. A track running on past its last junction is cut back to it (trim_overhangs). list_removed names every item that went.

Input parameters:

- `dangling_tracks` (boolean)
- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `duplicate_tracks` (boolean)
- `list_removed` (boolean)
- `refill` (boolean)
- `trim_overhangs` (boolean)
- `unconnected_vias` (boolean)
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `add_project_files` (~112 tokens)

Add files to the project

Unpack a ZIP into the project folder, keeping its paths: new footprints into a .pretty library the fp-lib-table names, 3D models, a library table. Existing files are kept unless overwrite is true; the reply lists written, replaced and kept files. Base64, up to about 18 MB zipped.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `overwrite` (boolean)
- `zip_base64` (string, required)

### `swap_footprint` (~215 tokens)

Swap footprints

Replace footprints in place with another footprint from a library in the project's fp-lib-table (library:name): the reference, value, position, rotation (or rot_deg), side, lock and schematic link stay, and nets move pad by pad. pad_map maps a NEW pad number to the OLD pad whose net it takes, for packages numbered differently. The schematic symbols' Footprint fields are updated too. Reports new pads left without a net and old nets left behind.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `swaps` (array, required)
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `fill_zones` (~126 tokens)

Fill zones

Refill every copper zone with KiCad's zone filler.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `stamp_silkscreen` (~343 tokens)

Stamp silkscreen

Silkscreen stamps for release, both off unless asked for: a small spec badge ("routed with Koppar", optionally the title, revision and part count) in the largest free patch of the front or back silk, and JLCPCB's JLCJLCJLCJLC placeholder on the back silk so their order number is printed there, not on the front. Free means clear of pads, mask openings, other silk, courtyards, holes and the edge. KiCad's DRC is run before and after and a stamp that changes any count is taken off again.

Input parameters:

- `badge` (boolean): Place the spec badge (default false).
- `badge_side` (string): Silk side for the badge; the larger free patch when unset.
- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `jlc_order_number` (boolean): Place JLCJLCJLCJLC on the back silk (default false).
- `parts` (integer): Part count for the badge; counted from the board when unset.
- `revision` (string): Revision for the badge ("rev B").
- `title` (string): Board title for the badge's second line.
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `tie_rail_pads` (~317 tokens)

Tie plane-net pads together

Tie neighbouring same-net SMD pads of the plane nets (GND, the rails with a pour) together on their own layer with short tracks, so a group shares one via to the plane instead of one via per pad, as a designer does. A tie is placed only where it misses every other net's pad, its tracks and vias, and the board edge. Before routing: route afterwards with preserve_existing (the default). After routing and prune_vias: run prune_vias on those nets again.

Input parameters:

- `avoid_copper` (boolean): Treat other nets' tracks and vias as obstacles (default true).
- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `layers` (array): Copper layers to tie on (default F.Cu and B.Cu).
- `max_mm` (number): Longest tie (default 2.5).
- `nets` (array): Nets to tie (default: every net that has a pour).
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…
- `width_mm` (number): Tie track width (default: the board's current track width).

### `widen_nets` (~336 tokens)

Widen power nets in place

Grow the tracks (and optionally vias) of the named nets in place, each as wide as its clearance to every other net's copper, holes and the board edge allows, up to the net's target width. Nothing moves and no via is added, so the score does not change. Routers neck power down to the signal width wherever the class width did not fit their grid; most necks have room around them. List the heaviest current first: earlier nets take the room. Pours are refilled after each net and a widening that leaves the board less connected is backed out. The result names what still holds each remaining neck (a neighbour to move or reroute).

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `guard` (boolean): Refill pours and back out widenings that disconnect anything (default true).
- `necks` (integer): How many remaining necks to report per net (default 12).
- `nets` (object, required): Net -> target track width in mm.
- `vias` (object): Net -> [diameter_mm, drill_mm] sizes to try, largest first; a via only ever grows.
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `finish_board` (~357 tokens)

Finish the open nets

Close what the router left open the way a designer does: for each open net the diagnosis names the copper boxing it in; that copper is ripped (never a poured net), the open nets are routed FIRST into the space, then the ripped nets go back around them; up to `rounds` rounds, each kept only if KiCad counts fewer unconnected items. Use it after route_board leaves a handful of nets open (route_board's default pipeline already runs three rounds; this adds more, or follows a single route); repair_board never moves the blockers.

Input parameters:

- `class_vias` (boolean): Route with the Default class's via instead of the board's smallest legal one.
- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `ml_options` (object)
- `reach_mm` (number): Radius cleared of tracks and vias around a pad with no way out (default 1.5).
- `rounds` (integer): Rip-and-reroute rounds (default 3).
- `router` (string)
- `time_budget_s` (integer): Router budget per routing call (default 120).
- `vias_in_pads` (string): 'allow': vias may sit in pin pads (the board must be ordered with filled and capped vias).
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `bridge_islands` (~214 tokens)

Join pour islands

A filled pour cut into islands by routing: one through-via per island that KiCad finds cut off from its net, placed well inside the island and inside the net's main copper on another layer, clear of every other net between. Reports the islands it found no site for. Run run_drc afterwards.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `max_vias` (integer)
- `nets` (array): Net names; * and ? wildcards, e.g. ["USB_D*", "+3V3"].
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `tidy_copper` (~223 tokens)

Tidy the copper

After routing: every run redrawn as the fewest 0/45/90-degree segments that clear, and every track narrower than its net's netclass width widened where it fits (slid sideways, bumped around a lone obstacle, or necked only over the stretch that needs it; a via or thin track of another net moved aside when that is all that is in the way). No via is added or removed; a change that would split a pour is undone, and the board is kept only if KiCad counts nothing worse.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `polish_vias` (~497 tokens)

Fewer vias, net by net

After route_board and prune_vias: rip one net at a time, most vias first, route it alone around everything else at a high via price, and keep the new copper only when KiCad counts fewer vias with no new open item or DRC error (a reroute that cuts a pour into islands first gets one via per island, bridge_islands). Run run_drc and get_score afterwards; a second pass sometimes finds more.

Input parameters:

- `bridge_islands` (boolean)
- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `max_nets` (integer): Nets to try, most vias first (default 40).
- `min_vias` (integer): Only nets with at least this many vias (default 2).
- `ml_options` (object)
- `nets` (array): Net names; * and ? wildcards, e.g. ["USB_D*", "+3V3"].
- `pairs` (boolean): Rip and reroute a differential pair (_H/_L, _P/_N, +/-) together (default true: a leg rerouted alone comes back at its own length; a step that degrades a pair is never kept).
- `pours` (boolean): Also polish the poured nets (default false): the pour and its stitch vias stay, the net is routed as a track tree on top, then its redundant stitch vias are pruned. A lottery: the tree that did this…
- `router` (string)
- `time_budget_s` (integer): Router budget per net (default 120).
- `total_budget_s` (integer): Stop starting nets after this (default 1800).
- `via_cost` (number): Via price for the lone reroute (default 60).
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…
- `workers` (integer): prune workers for a poured net (default 4).

### `couple_pairs` (~413 tokens)

Couple differential pairs

After route_board: re-route the weakly coupled differential pairs one at a time, least coupled first. Both legs are ripped and routed alone around everything else as a pair; the new copper stays only when the pair's coupled share rises by min_gain_pct, its skew stays within max_skew_mm, KiCad counts no new open item or DRC error, and the board gains at most max_extra_vias vias. Pairs routed with the whole board lose their lanes; alone they couple. Run check_net_rules before and after.

Input parameters:

- `bridge_islands` (boolean)
- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `max_extra_vias` (integer): Vias a kept reroute may add to the board (default 2).
- `max_skew_mm` (number): Largest length mismatch kept (default: the pair's current skew, at least 1 mm).
- `min_gain_pct` (number): Coupling points a reroute must gain to be kept (default 10).
- `ml_options` (object)
- `pairs` (array): Only pairs with a leg matching these (default every pair under target_pct).
- `target_pct` (number): Pairs coupled below this are tried (default 70).
- `time_budget_s` (integer): Router budget per try (default 90).
- `total_budget_s` (integer): Stop starting pairs after this (default 1800).
- `tries` (integer): Router seeds per pair; the best acceptable one is kept (default 2).
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `diagnose_open_nets` (~271 tokens)

Why nets do not route

For every net still open (or the nets named): each pad with the escape corridors free on its own layer, whether a via can be dropped beside it at all, and what blocks it (which part's pads, which net's tracks or vias, the board edge). A pad with no free corridor and no via site is CRAMPED — no router can reach it; the advice names the parts to move. Otherwise the advice says which nets to rip and route first. Use it instead of repeating repair_board on a net that keeps failing.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `max_nets` (integer)
- `nets` (array): Only these nets (default: every open net).
- `reach_mm` (number): How far a corridor must stay free (default 1.5).
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `run_drc` (~247 tokens)

Design-rule check

KiCad's DRC on the board as it is now, with schematic parity when the project has its schematic: error and warning counts by type, shorts, unconnected items, parity items, and the first violations with their items and positions (types filters, max_violations caps; default 40). Also mount_fit: parts reaching through the board (mid-mount jacks, USB-C) checked against their cutouts from their 3D models, with any body area over board material or within the fab's 0.2 mm milling tolerance of the cut.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `max_violations` (integer)
- `types` (array)
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `render_board` (~342 tokens)

Render the board (2D, exact)

An exact 2D picture of the board as an engineer reads it: copper per layer (the facing layer full strength, the others faded), pads, vias, pours, outline, courtyards and refs. side top|bottom, region [x, y, w, h] mm for a crop, drc_markers to circle every DRC violation, ratsnest to draw the open connections, highlight_nets/highlight_refs in magenta. The pixel-per-mm scale and region come back so a follow-up crop is exact. Download workspace.render.png.

Input parameters:

- `courtyards` (boolean)
- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `drc_markers` (boolean)
- `highlight_nets` (array)
- `highlight_refs` (array)
- `layers` (array)
- `markers` (array)
- `max_width` (integer)
- `px_per_mm` (number)
- `ratsnest` (boolean)
- `refs` (boolean)
- `region` (array): [x_mm, y_mm, w_mm, h_mm] crop; default the whole board.
- `side` (string)
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `export_step` (~141 tokens)

Export STEP

Export the assembled board as STEP (3D models, DNP parts left out). Download it as workspace.step; workspace.zip includes it.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `list_board_revisions` (~71 tokens)

Board revisions

The snapshots of this board, newest first. Revision N is the board as it was before change N (revision 0 is the project as imported); restore_board_revision N goes back to it.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.

### `restore_board_revision` (~159 tokens)

Restore a revision

Put the board and its rules back as they were in a revision from list_board_revisions. The current board is saved as a new revision first, so the restore itself can be undone.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `revision` (integer, required)
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

### `get_board_job` (~143 tokens)

Board job

The design's latest board job: its status and, once it ends, its result or error. wait_s holds the call until it ends.

Input parameters:

- `design_id` (string, required): The design id returned by import_kicad_project or list_designs.
- `wait_s` (integer): Seconds to wait for the job (default 55). A job still running comes back with status "running": follow it with get_board_job. A job is allowed the time its budget asks for (time_budget_s, total_budge…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-koppar-koppar/app#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 80
- 2026-10-28: 80
- 2026-10-27: 80
- 2026-10-26: 79
- 2026-10-25: 79
- 2026-10-24: 79
- 2026-10-23: 78
- 2026-10-22: 78
- 2026-10-21: 77
- 2026-10-20: 77
- 2026-10-19: 76
- 2026-10-18: 76

## Common questions

### What is the Koppar MCP server?

Koppar is an MCP server listed in the public MCP registry as ai.koppar/koppar. Design a KiCad PCB from a prompt: parts, schematic checks, routing, KiCad DRC and Gerbers. This page covers its hosted endpoint (https://app.koppar.ai/mcp).

### Is the Koppar MCP server safe to use?

Koppar scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Koppar MCP server expose?

Koppar exposes 65 tools: get_workflow_guide, create_design, leave_feedback, list_designs, delete_design, and 60 more. Their descriptions and schemas cost roughly 16,262 tokens of context every time the server is loaded.

### Does the Koppar MCP server require authentication?

Yes. Koppar asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Koppar MCP server still maintained?

Koppar is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://app.koppar.ai/mcp
- Authorisation metadata: https://app.koppar.ai/.well-known/oauth-protected-resource/mcp
- Website: https://docs.koppar.ai/agents/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-koppar-koppar/app.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-koppar-koppar/app.json
- HTML version of this page: https://verifymcp.io/servers/ai-koppar-koppar/app
