AI PCB design, layout, and routing
Listed on
First seen 17 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.
3
Directories
Collected by InvokeRank
16
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
1
GitHub stars
From MCP Toplist
Tools
| Tool | Description | Behaviour |
|---|---|---|
| check_board_layout | Checks a saved PCB layout at expectedRevision for manufacturing or layout review. create_board and update_board already return this check as validation when their layout finished in time; call this when validation is null while layout.current is true. Its geometry and applied electrical requirements must both be current. A missing or stale layout must complete first: follow the job a save started with get_generation, or call generate_layout when none is active. electrical_requirements_not_applied also requires a completed regeneration before checking or manufacturing export. Reuses a current assessment or computes and saves one, which requires write access and normal compute capacity. If the board changes during the check, read get_board again. Returns hasBlockingIssues and actionable blockingIssues; no numeric score or deductions. | Changes data |
| create_board | Creates a saved board from published catalog parts and verified pins: its schematic, its size and the position of every part and designator. Saving also routes and checks the board: this call waits for that and returns the board as it is afterwards. Supply a fresh private boardRef, name, requestId, intent and boardEdits. To make boardRef, generate 32 random bytes locally, encode as unpadded base64url and prepend egbr1_. The server uses the connected account when available; otherwise it establishes private board access automatically. Keep this SAME boardRef for all later reads, edits, status and export calls. Store it in this conversation or supported private execution state before submitting; do not discard it between isolated calls. Identical retries with the same boardRef, requestId and arguments recover the original creation. Do not use a new reference to recover existing work. Return the complete private board link to this user after creation so later turns can continue it; never log private references or put them in source files. Server defaults supply the other settings, footprints, models and manufacturing limits; change them only when the request asks. Account boards are personal unless organizationId is specified. Use the returned revision for later edits. validation lists any blocking issues to fix; if it is null while layout.current is true, call check_board_layout. If the result has pollAfterSeconds, the layout is still running: follow generation with get_generation using the same boardRef, then use its boardRevision and call check_board_layout. If layoutNotStarted is returned instead, the board is saved but its layout did not start; call generate_layout after any stated wait. Use update_board for existing work. Thin intent format: each parts entry is an array of strings [id, dbId, value], with an optional fourth designator. Choose id as the design-local part ID; copy dbId from the catalog result's id; value is the required value/display label. Omit the fourth designator when it matches id. Each connections entry is {net, class, pins}; class is power, signal, or ground. Each pins entry is [partId, padId]: use the design-local part ID and copy padId from the catalog result's pins[].number, both as strings. Optional pinCurrentRequirements uses those same partId and padId identities with requiredCurrentA in amperes and direction into, out, or bidirectional relative to the net. Omit the list to retain existing values; a supplied list replaces it, and [] clears it. Placement: nothing is placed or sized automatically. Board coordinates are mm from the lower-left corner of the board (of its bounding box for a circle or an outline), x right and y up. boardEdits gives the board a size (settings.width and settings.height in mm, a circle diameter, or an outline), a fixedPlacements entry {partId, x, y, rotationDeg, side} for every part, and a silkscreenTexts entry {id: "refdes_<partId>", x, y} for the reference designator of every part. Catalog results that carry pins also carry geometry in mm at rotation 0 on the top side, x right and y up from the footprint origin: body [width, height], extent [minX, minY, maxX, maxY] of everything the footprint occupies, pins {number: [x, y]} and a connector's opening; call get_part when a chosen part has none. Compute positions from these numbers, rotating them with the part. Keep every extent inside the outline with 1 mm to spare and 1 mm from other extents, more where traces must pass; a rectangle has corners rounded to a 2 mm radius unless settings.roundedCorners is false, and an extent in a corner must clear that curve too. An external receptacle sits at a board edge with its opening outward. Put connected parts next to each other and support parts at the pins they serve. A designator is positioned by the centre of its text and counts as 0.8 mm per character wide and 1 mm tall: keep it at least 0.2 mm outside every part's extent, 0.3 mm inside the outline and 0.2 mm from other labels, within 3 mm of its own part and at least 0.3 mm nearer to it than to any other part. Each of these distances is measured from the box the text covers to a part's extent, not between centres. Size the board to the arrangement. Measured conflicts come back as issues naming the parts; fix those and resubmit. settings.layers defaults to auto: the layout chooses one or two copper layers and saves its choice as the board's layers, which later layouts keep until an edit sets settings.layers again. If validation rejects the proposal, preserve the schematic and valid catalog parts, correct the returned detailed issues, and keep the same boardRef. Use a new requestId when input changes; reuse the same requestId and arguments for an unchanged retry. Research again only when an issue needs missing part or pin information. | Changes data |
| delete_board | Permanently deletes the specified saved account board when the user requests its removal. Requires explicit boards:delete authorization and personal ownership or organization owner/admin access; guest boards are unsupported. Read get_board first and pass its current revision. Deletion cancels active generation jobs and cannot be undone. A revision conflict requires reading the board again. Missing, already deleted or inaccessible boards return the same not_found error; this does not confirm that an earlier request succeeded. No requestId or replay receipt is supported. | Destructive |
| export_board | Creates a stable private download of a saved board as a manufacturing ZIP or editable .egb project backup. Pass the latest saved revision as expectedRevision. Use format egb directly for project backups, including empty or incomplete projects and unapplied geometry or electrical changes; no layout generation or check is required. Manufacturing ZIPs require a current saved layout with applied electrical requirements; generate and wait for completion when needed, then read the new revision. New exports require current board access. Issued download links have no automatic expiry and retain this exact export after board edits, deletion, guest claim or cleanup. Only explicit download-link revocation or deletion of the exported file ends access. Keep each complete private URL unchanged, including its fragment; anyone with it can download the file. | Changes data |
| generate_layout | Starts one durable layout job for boardRef at expectedRevision and waits for it: returns generation completed with the new boardRevision, or still queued or running with pollAfterSeconds to follow with get_generation. A completed layout is not yet checked; call check_board_layout with that boardRevision. The job routes the board as it is placed; a board with a part that has no position, or without a size, is refused until update_board supplies them. create_board and update_board start the layout job themselves, so call this only to retry: after a failed or cancelled layout, after a save returned layoutNotStarted, or to regenerate a current layout. If a layout of that same revision is already running or was just saved, returns that job instead of starting another. Use the latest revision from get_generation or get_board. Read status with get_generation using the same boardRef; do not regenerate to inspect progress. Successful completion replaces the saved layout. A requestId supports IDENTICAL retries only; changed arguments need a new requestId. revision_conflict requires get_board; board_busy identifies the existing job to poll. Subject to normal compute capacity and board complexity limits, without AI credits. | Destructive |
| get_board | Reads the current revision, thin schematic, supported settings, physical context, layout freshness and latest layout job from one saved-state snapshot. Reading never saves or moves a board: a private board has ownerUserId null and a private link as url, while a board in an account has an owner and a /boards/ url; use save_board_to_account to keep a private board in the connected account. Use the same boardRef before editing, checking or exporting. A completed older job does not imply a current layout. validation is the saved outcome of check_board_layout for the current layout; null means that layout has not been checked, not that it passed. Use get_generation with boardRef for status, never generate_layout as a status probe. includePreview optionally adds a saved-layout image; previewing does not change the board design or revision. Normal compute capacity limits apply. | Read-only |
| get_generation | Reads stored layout generation status using the same boardRef; needed only while a create_board, update_board or generate_layout result has pollAfterSeconds. Omit generationId to read the active/latest layout job; supply it only to inspect that exact job. Returns generation:null if no layout job exists. While queued or running, wait pollAfterSeconds; stop polling at completed, failed or cancelled. boardRevision is the current saved revision, which a completed layout advances; use it for the next edit, check or export, or read get_board for the saved layout. Never call generate_layout to inspect status. Polling does not save private work to an account. | Read-only |
| get_part | Returns a published catalog part and verified pins. Skip this call when search_parts already supplied the needed pins and facts. Use the selected catalog result’s id; returned pins[].number is the padId used in board connections. Use search_parts to find alternatives. factQuery and factOffset select or page cached datasheet facts. An optional boardRef applies that board’s strict Part List restriction, when enabled. | Read-only |
| get_profile | Returns the connected account identity. Requires account authorization; unauthenticated calls request OAuth. Public catalog browsing and creating a new board do not require probing account identity. | Read-only |
| list_boards | Lists accessible boards with their private boardRef, most recently updated first. A supplied boardRef selects only that board. Account access returns personal boards unless organizationId is specified. Without access, returns guidance, not a claim that an account has no boards. Continue existing work using its original boardRef or owning account. Continue with nextOffset until null, then use get_board for the selected board. | Read-only |
| list_organizations | Returns the connected account’s organizations and membership roles. Requires account authorization. Use the returned organizationId with list_boards or create_board for organization work; omit organizationId for personal boards. | Read-only |
| save_board_to_account | Saves a private board into the connected EasyGerber account when the user asks to keep it there. Requires account authorization; an unauthenticated call requests sign-in. Supply the same boardRef. The board must have no layout running: wait for get_generation to finish, then retry. Saving copies the design and its layout into a personal account board and retires the anonymous access, which cannot be undone. The result is that account board, with a new id and revision to use from now on. Keep the same boardRef; after a save it works only while this account is connected. A board already in the account is returned unchanged. | Destructive |
| search_parts | Searches published catalog components. Supply known catalog filters such as category and exact package. Use query for the remaining terms or exact MPN. Put electrical bounds and applicable test conditions in requirements. Use forwardVoltage for LED Vf. Use candidateIds to check previously found parts under the same constraints. Reuse a qualified candidate’s catalog ID. On mismatch, check the next candidate. For unknown, verify the exact part’s datasheet at the required conditions or leave the requirement unresolved. The first candidate includes verified pins when available; other candidates may omit them. Reuse returned IDs, pins and facts; call get_part only when the selected candidate lacks needed pins or facts. factQuery selects cached facts for the matching candidates. Include boardRef on every lookup for a board with a strict Part List. If results are unrelated, make at most two retries with simpler text, preserving every required filter, specification and board restriction. If none qualifies, report the unmet requirement. | Read-only |
| stop_generation | Cancels a queued or running layout generation belonging to the specified board; use get_generation when only checking progress. A completed, failed or already cancelled job retains its terminal status. Cancellation cannot be undone; starting again requires a new job. It can update the saved board revision, so read get_board before further edits. A later job is unaffected. | Destructive |
| submit_feedback | Sends a bug report, feature request or general feedback to EasyGerber only when the user asks or agrees to report it. Send only the approved message; never automatically attach private board content, raw diagnostics, transcripts or exports. No account, board or guest session is required. A connected account attributes the report to that account; otherwise an optional existing guestToken attributes it to that guest. Reuse requestId with the identical category and message on retries. Returns a submission receipt, without promising a response. Account feedback is limited to 10/hour and 50/day; guest and anonymous feedback share those limits by network. | Changes data |
| update_board | Edits a saved board at expectedRevision, the revision the last save or read returned; supply at least one of name, intent or boardEdits. Read get_board first when you do not hold the current board. Omitted fields are preserved; schematic edits require the complete replacement thin intent, while boardEdits is a physical patch. Parts and designators stay where they are unless the edit moves them; an edit that adds a part positions it and its designator in boardEdits, and a removed part's position and designator go with it. Schematic changes discard the old layout and physical changes make it stale; either way this save routes and checks the board again, waits for that and returns the board as it is afterwards. Use the returned revision next. validation lists any blocking issues to fix; if it is null while layout.current is true, call check_board_layout. If the result has pollAfterSeconds, the layout is still running: follow generation with get_generation, then use its boardRevision and call check_board_layout. An edit made while a layout is running replaces that job with one for the edited board. If layoutNotStarted is returned instead, the edit is saved but its layout did not start; call generate_layout after any stated wait. A stale expectedRevision requires a fresh get_board. Thin intent format: each parts entry is an array of strings [id, dbId, value], with an optional fourth designator. Choose id as the design-local part ID; copy dbId from the catalog result's id; value is the required value/display label. Omit the fourth designator when it matches id. Each connections entry is {net, class, pins}; class is power, signal, or ground. Each pins entry is [partId, padId]: use the design-local part ID and copy padId from the catalog result's pins[].number, both as strings. Optional pinCurrentRequirements uses those same partId and padId identities with requiredCurrentA in amperes and direction into, out, or bidirectional relative to the net. Omit the list to retain existing values; a supplied list replaces it, and [] clears it. Placement: nothing is placed or sized automatically. Board coordinates are mm from the lower-left corner of the board (of its bounding box for a circle or an outline), x right and y up. boardEdits gives the board a size (settings.width and settings.height in mm, a circle diameter, or an outline), a fixedPlacements entry {partId, x, y, rotationDeg, side} for every part, and a silkscreenTexts entry {id: "refdes_<partId>", x, y} for the reference designator of every part. Catalog results that carry pins also carry geometry in mm at rotation 0 on the top side, x right and y up from the footprint origin: body [width, height], extent [minX, minY, maxX, maxY] of everything the footprint occupies, pins {number: [x, y]} and a connector's opening; call get_part when a chosen part has none. Compute positions from these numbers, rotating them with the part. Keep every extent inside the outline with 1 mm to spare and 1 mm from other extents, more where traces must pass; a rectangle has corners rounded to a 2 mm radius unless settings.roundedCorners is false, and an extent in a corner must clear that curve too. An external receptacle sits at a board edge with its opening outward. Put connected parts next to each other and support parts at the pins they serve. A designator is positioned by the centre of its text and counts as 0.8 mm per character wide and 1 mm tall: keep it at least 0.2 mm outside every part's extent, 0.3 mm inside the outline and 0.2 mm from other labels, within 3 mm of its own part and at least 0.3 mm nearer to it than to any other part. Each of these distances is measured from the box the text covers to a part's extent, not between centres. Size the board to the arrangement. Measured conflicts come back as issues naming the parts; fix those and resubmit. settings.layers defaults to auto: the layout chooses one or two copper layers and saves its choice as the board's layers, which later layouts keep until an edit sets settings.layers again. If validation rejects the proposal, preserve the schematic and valid catalog parts, correct the returned detailed issues, and keep the same boardRef. Use a new requestId when input changes; reuse the same requestId and arguments for an unchanged retry. Research again only when an issue needs missing part or pin information. | Destructive |
| Directory | Listing | Tier | First seen |
|---|---|---|---|
| Claude | EasyGerber | community | 18 Oct 2026 |
| Official MCP Registry | EasyGerber: AI PCB design, layout, and routing | - | 17 Oct 2026 |
| GitHub MCP Registry | EasyGerber: AI PCB design, layout, and routing | - | 31 Oct 2026 |