EasyGerber MCP server
Commit Nov 14, 2026Enables AI agents to design, layout, route, and export PCB manufacturing files through hosted board-design tools.
Also known as EasyGerber/easygerber-agent-plugin, easygerber-agent-plugin
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.1
- Last commit
- Nov 14, 2026
- License
- —
What is EasyGerber MCP?
EasyGerber enables AI agents to design, layout, route, and export PCB manufacturing files through hosted board-design tools.
Summary generated from the project's README
About EasyGerber MCP server
EasyGerber provides a bridge between AI coding agents and hosted board-design tools to automate printed circuit board creation. It allows developers to use AI clients to design, layout, route, and export manufacturing files without running a local PCB engine. The service handles complex tasks like component placement, routing, and scoring on remote servers.
Users can connect via several methods depending on their needs. A guest mode is available through a general MCP endpoint that requires no sign-up or API keys, though it limits work to one private board per session. For saving progress or accessing organization boards, clients like Cursor, Antigravity, and Grok use an account-specific URL that requires OAuth authorization. The server supports various integration styles, including Streamable HTTP for Cline and Gemini CLI, and custom power installations for Kiro.
What you can do with it
- 1Search for electronic componentsUse the agent to find published parts for a new circuit design.
- 2Modify existing board designsInstruct an AI to open a saved board and perform specific edits or renames.
- 3Automate PCB layout and routingHand off the task of component placement and trace routing to an AI client.
Written from the project's README. Every use case is checked against a quote from it.
How to install EasyGerber MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall EasyGerber MCP in Claude Code
$ claude mcp add --transport http easygerber-agent-plugin https://www.easygerber.com/api/mcpInstall EasyGerber MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"easygerber-agent-plugin": {
"url": "https://www.easygerber.com/api/mcp"
}
}
}Install EasyGerber MCP in VS Code
.vscode/mcp.json
{
"servers": {
"easygerber-agent-plugin": {
"type": "http",
"url": "https://www.easygerber.com/api/mcp"
}
}
}Install EasyGerber MCP in VS Code CLI
$ code --add-mcp '{"name":"easygerber-agent-plugin","type":"http","url":"https://www.easygerber.com/api/mcp"}'Install EasyGerber MCP in Codex
$ codex mcp add easygerber-agent-plugin --url https://www.easygerber.com/api/mcpInstall EasyGerber MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.easygerber-agent-plugin] url = "https://www.easygerber.com/api/mcp"
Install EasyGerber MCP in Gemini CLI
$ gemini mcp add -s user --transport http easygerber-agent-plugin https://www.easygerber.com/api/mcpInstall EasyGerber MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"easygerber-agent-plugin": {
"url": "https://www.easygerber.com/api/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableeasygerber/easygerber-agent-plugin is public and reachablegithub.com/easygerber/easygerber-agent-plugin ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-12github.com/easygerber/easygerber-agent-plugin ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 168 msPass
README
View on GitHubEasyGerber: AI PCB design, layout, and routing
This package connects coding agents to EasyGerber's hosted board-design tools. Its public files contain workflow instructions, connection metadata, icons, and a small installer. Board layout, routing, and scoring run on EasyGerber's servers.
Version 0.3.9 simplifies the first starter example to request manufacturing files. The package uses one private board reference for creation and continued work. The service selects account ownership or private access automatically, exposes the current layout job for status reads, and preserves existing-client compatibility. Ordinary OpenAI sign-in explicitly requests only workflow permissions; deletion remains a separate consent. Hosted tools and package instructions must both be current; package checks alone do not establish a live client workflow.
Source is available in the public integration repository. The npm installer and platform plugin packages have separate client-validation processes and share the EasyGerber workflow skill and hosted service.
Start without signing up
Use https://www.easygerber.com/api/mcp to search published parts and create a board without signing up. The agent uses one private boardRef for creation, edits, layout, checks, previews, and exports. The service uses the connected account when valid or establishes private access automatically. There is no user-facing guest setup or separate token to manage. Keep the private board link out of public messages and repositories.
| Connection URL | When to use it | Sign-in |
|---|---|---|
https://www.easygerber.com/api/mcp |
General MCP connections and guest-first directory listings | Not required for guests; required for account boards, organization access, and saving a guest board to an account |
https://www.easygerber.com/api/mcp/account |
Saved account boards in clients that request OAuth only during setup | Required before initialization or tool discovery; this connection does not start in guest mode |
The Codex installer, OpenAI packages, and Claude package use the general URL. The Grok account connector and native Cursor and Antigravity configurations below use the account-only URL. For a new guest connection, leave authentication unset; a rejected existing account credential must be reauthorized and will not silently become a guest connection. See Create and continue without signing up for private access and account transitions.
Grok
Connect your EasyGerber account once to open and edit saved boards in consumer Grok:
- In Grok, open Plugins → New Connector → Custom.
- Name the connector EasyGerber and enter
https://www.easygerber.com/api/mcp/accountas the server URL. - Complete EasyGerber sign-in and choose Allow access. Then ask Grok to open a saved board by its EasyGerber URL and make your requested changes.
For example: “Open this saved EasyGerber board: [your board URL]. Rename it to LED indicator and read it again to confirm the change was saved.”
This account entry requires authorization during connection setup and uses the existing EasyGerber tools and account permissions. For a new connection to the account entry, complete its normal sign-in flow. Existing published package configurations continue to use /api/mcp, which supports guest use and optional account authorization.
On October 16, 2026, consumer Grok completed consent, read an existing private saved board, saved a temporary name change, and restored the original name. Both changes were confirmed after reopening the board on the EasyGerber website. Grok Bot has not been tested. Browser 3D rendering was not verified because WebGL was unavailable in the test browser. This consumer check does not establish Grok Build's interactive OAuth or model-driven board workflow.
Cursor
The public repository includes a native .cursor-plugin/plugin.json manifest. It uses the shared EasyGerber skill and artwork and connects to https://www.easygerber.com/api/mcp/account. This entry requires account authorization before tools become available; complete EasyGerber sign-in and choose Allow access in Cursor's connection flow. Account permissions, plan limits, and generation billing still apply.
To load a checkout of the public repository in the official Cursor CLI:
agent --plugin-dir .
Enter /mcp, select Easygerber (plugin), and choose Manage Server → Login to complete the browser consent flow. Then ask: “Open this saved EasyGerber board: [your board URL]. Read its current name and components.” Cursor manages the account credentials. The npm installer is not required; it configures Codex only. The root OpenAI and Claude connection configurations retain guest-capable /api/mcp access. Marketplace publication is subject to Cursor review.
Antigravity
Design and lay out PCBs in Antigravity using published components, automatic placement and routing, schematic editing, and manufacturing exports. The public repository includes native Antigravity metadata and the shared EasyGerber skill. Its MCP connection uses https://www.easygerber.com/api/mcp/account; account permissions, plan limits, and generation billing still apply.
Install the plugin from the public repository with the current Antigravity CLI and start a session:
agy plugin install https://github.com/EasyGerber/easygerber-agent-plugin
agy
Use /mcp to inspect the EasyGerber connection. Complete EasyGerber sign-in and choose Allow access when Antigravity requests account authorization. Then ask: “Open this saved EasyGerber board: [your board URL]. Read its current name and components.” Antigravity manages the account credentials. The npm installer is not required. Marketplace publication is subject to Antigravity review.
See the official plugin guide and MCP guide.
Cline
Cline can connect directly to EasyGerber's hosted MCP endpoint using Streamable HTTP. Use an existing Cline installation with a configured model. The npm setup installer in this repository configures Codex only; it is not the Cline installation path. No local EasyGerber server, build, or API key is needed for a new guest connection.
In the Cline IDE panel, open MCP Servers → Remote Servers, enter EasyGerber as the server name and https://www.easygerber.com/api/mcp as the server URL, choose Streamable HTTP, and select Add Server. Leave authentication unset for guest access.
Alternatively, open MCP Servers → Configure → Configure MCP Servers and merge this entry into the existing mcpServers object, preserving other servers and settings:
{
"mcpServers": {
"easygerber": {
"type": "streamableHttp",
"url": "https://www.easygerber.com/api/mcp",
"disabled": false,
"autoApprove": []
}
}
}
The explicit streamableHttp type matters: omitting it selects legacy SSE in Cline. Keep tool approval enabled. If easygerber already exists, inspect that entry instead of replacing it or creating a duplicate.
With the current Cline CLI, the equivalent configuration command is:
cline mcp add easygerber https://www.easygerber.com/api/mcp --transport http --yes
This command saves the connection; it does not by itself prove successful setup. In Cline, verify that the connection succeeds and EasyGerber tools such as search_parts, get_part, and create_board appear. For an installation-only check, stop after tool discovery; do not start a guest session, create or modify a board, generate a layout, export files, or send feedback.
For later user-requested board work, guest access supports one board per session before signup. Saved account boards require EasyGerber OAuth consent. Clients that require authorization during connection setup can use the separate https://www.easygerber.com/api/mcp/account entry described above. Account authorization and board workflows need their own Cline validation; the guest connection check does not verify them.
These instructions follow the official Cline MCP guide. On October 18, 2026, Cline CLI 3.0.73 read the proposed README and wrote the native connection configuration into an empty isolated profile with tool approvals enabled. A separate check using its installed @cline/core 0.0.95 connected and discovered 17 EasyGerber tools without authentication. The agent itself did not verify discovery. No EasyGerber tool was called; OAuth and board operations were not tested.
Kiro
Install the Kiro power folder through Powers → Add Custom Power, or run kiro-cli --v3 powers install ./kiro from a local checkout of this public repository and start kiro-cli --v3. The npm installer is not needed. The power uses the guest-capable /api/mcp entry and includes the complete EasyGerber workflow in its skill.
On October 18, 2026, Kiro CLI 2.32.0 V3 imported and explicitly activated the power, read its complete skill, and discovered 17 hosted tools without EasyGerber authentication. Its native guest workflow selected published parts, created and revised a board, completed layout generation, read preview data, checked for blockers, and exported manufacturing and EasyGerber files. A separately configured /api/mcp/account connection completed OAuth and successfully saved that guest board to a personal account after resuming the same conversation; a subsequent read confirmed the account board and its saved layout. A separate browser check rendered the saved board's 3D parts.
The power's automatic mid-session OAuth did not complete in this CLI version. Use the optional account connection and resume instructions in the Kiro README for account work and guest-board saving. Complete browser consent while Kiro's local callback listener is active; an earlier account-endpoint attempt expired after about 60 seconds, separately from the power's mid-session authorization-state error. Token refresh, deletion, feedback, and keyword-only activation remain untested in Kiro. Directory approval is separate from these checks.
Gemini CLI
Install the EasyGerber extension in the current Gemini CLI. Gemini's model sign-in is separate from EasyGerber: a new EasyGerber guest connection needs no account or API key.
gemini extensions install https://github.com/EasyGerber/easygerber-agent-plugin
gemini extensions list
gemini skills list
gemini mcp list
Review the extension's MCP connection and accept the normal installation prompt. Restart an existing Gemini session after installation. Confirm that the easygerber extension and shared skill are enabled and that the EasyGerber MCP connection is available. Existing user or workspace settings with the same server or skill name can take precedence over an extension; inspect them if the displayed connection or skill comes from another source.
The extension connects to https://www.easygerber.com/api/mcp using Streamable HTTP and loads the existing skills/easygerber workflow. It includes no local EasyGerber server or engine. Keep Gemini's normal tool approval prompts enabled. Try: “Use EasyGerber to create a board from the pin assignments in this firmware.” The agent selects published components and uses the guest workflow described above.
Verified with Gemini CLI 0.65.0: extension installation, shared-skill discovery, and an active MCP connection. A separate check using that installed CLI's MCP transport discovered 17 tools and completed guest-session creation, published-part search, and part lookup. This check did not exercise an interactive model session, board creation, layout, export, or account authorization.
For saved account boards or saving an existing guest board to an account, Gemini documents the interactive /mcp auth easygerber command. Complete EasyGerber consent, then resume the original task and guest-board claim if applicable. Guest discovery does not verify account OAuth, token refresh, or automatic authorization during a tool call. See Gemini's MCP authorization documentation.
The extension is distributed through this repository and its dedicated Gemini release archive. To update an installed copy, run gemini extensions update easygerber. The gemini-cli-extension repository topic enables the gallery's daily discovery process; gallery indexing is separate from publication and is not Google endorsement or distribution in the consumer Gemini app.
Devin
The public source export includes .devin-plugin/plugin.json, which connects to the guest-capable https://www.easygerber.com/api/mcp endpoint and loads the existing skills/easygerber workflow and artwork. Devin's own account sign-in is separate from EasyGerber authorization. A new EasyGerber guest connection needs no account or API key.
For local validation, use a checkout of the exported public integration repository with a signed-in Devin CLI:
devin plugins install --local .
devin
Start a new session after installation and use /easygerber:easygerber to load the workflow. Keep normal tool approvals enabled. For a minimal catalog check, ask: “Use EasyGerber to find a published two-pin connector and confirm its catalog pins. Do not create a board.” The agent uses the public catalog tools without starting a guest session or requesting account authorization.
On October 20, 2026, Devin CLI 3000.11.92 installed the generated local package and discovered its shared skill and hosted MCP configuration. A fresh native session using the Free account's available SWE-1.6 Slow model created one guest session, searched published connectors, and read a returned part to confirm its two catalog pins. No board creation, layout, export, or EasyGerber account authorization was tested. The earlier SWE-2 attempt required Pro and stopped before calling a tool; no paid upgrade was purchased. Marketplace review and listing remain separate from these native checks.
Devin documents devin mcp login easygerber for plugin OAuth connections. Account access, guest-to-account continuation, and board workflows need separate native validation; installing a plugin or listing tools does not establish those results. Marketplace submission and listing are separate from the shared package's release checks. See the official Devin plugin guide.
Factory Droid
Add EasyGerber's vendor marketplace and install the plugin in Droid:
droid plugin marketplace add EasyGerber/easygerber-agent-plugin
droid plugin marketplace list
droid plugin install easygerber@easygerber-agent-plugin --scope user
Read back the registered marketplace name with marketplace list; pinned sources can have a different name. This vendor catalog references the existing claude/ package. Droid supports that layout and translates its metadata and MCP configuration while caching it. No local EasyGerber engine or npm installer is needed.
Use a configured Droid model and keep normal tool approvals enabled. Initial catalog access and a new board use https://www.easygerber.com/api/mcp without an EasyGerber account. Saved-account work requires separate EasyGerber consent and the permissions described below. Installing the plugin does not verify its account authorization or complete board workflow. Vendor-marketplace availability is separate from inclusion in Factory's own catalog. See the official Factory plugin documentation.
Codex in VS Code or the terminal
Requires Node.js 22 or newer and Codex. These npm commands require version 0.3.8 to be published to npm; check npm view @easygerber/agent-plugin version first. If npm is behind the source release, use the source installation instructions below.
npx @easygerber/agent-plugin@0.3.8 setup --dry-run
npx @easygerber/agent-plugin@0.3.8 setup
npx @easygerber/agent-plugin@0.3.8 doctor
Setup installs ~/.agents/skills/easygerber and adds a small managed MCP table to $CODEX_HOME/config.toml (default ~/.codex/config.toml). It preserves existing TOML text and other servers. An ownership receipt lives in ~/.easygerber/agent-plugin/codex-install.json. No project files or firmware are changed. Codex is the default and only installer target; optional --client codex makes that choice explicit. All commands support unattended use, and --yes is accepted for scripts.
Restart the Codex chat/IDE after setup, then ask: “Create a small 3.3 V LED board, show a preview, and export the manufacturing files.” The agent uses your connected account or starts a guest board automatically through https://www.easygerber.com/api/mcp.
For your saved account boards or organization work, connect EasyGerber from MCP settings. If Codex CLI is installed, run:
codex mcp login easygerber
The client opens the account authorization flow and stores its credentials. The managed MCP configuration requests boards:read, boards:write, boards:generate, boards:export, and offline_access, so account consent covers ordinary board workflows and renewable access, without deletion. The OpenAI plugin also sets these as explicit defaultScopes, overriding scopes otherwise inferred from all advertised tools; additive baseScopes would not exclude deletion. See the OpenAI OAuth configuration reference. Deletion requires separate, explicit boards:delete consent; an existing boards:write grant is insufficient. Organization permissions, account limits, and the user's consent still control account access. The installer never asks for, reads, or stores access tokens or guest capabilities. doctor checks local configuration and skill integrity; it does not prove that authentication, guest mode, or the live service works.
Try: “Use EasyGerber to create a board from the pin assignments in this firmware.” The agent reads relevant local code, selects published parts, and sends board requirements through the MCP service. Ordinary account scopes are boards:read, boards:write, boards:generate, and boards:export; organization permissions, quotas, and billing still apply.
Create and continue without signing up
Public search_parts and get_part calls need no board or account. A board-scoped lookup uses its boardRef and preserves the board's strict Part List. For each new board, the agent generates a private reference once: egbr1_ plus 32 cryptographically random bytes encoded as unpadded base64url. It sends that reference with the normal name, intent, and UUID requestId to create_board. The service saves an account-owned board when valid account access exists or establishes private access automatically. Subsequent board tools use the same reference, without coordinating a board UUID and a separate guest token.
A stateless client must retain this one reference in private tool context. After an uncertain creation result, it replays the exact original reference, request ID, and arguments; the service returns the original result without another board. Existing work must never be replaced because a reference was lost or rejected. Public UUIDs, request IDs, IP addresses, and client labels do not grant access. The reference is never a user-facing setup question and must not appear in source files, diagnostic logs, analytics, or public support requests. Account references still require the owning account's authorization.
Reads expose the current saved revision, layout freshness, and current generation. A client can read get_generation with the board reference alone when it does not have the job ID. It should not submit another generation as a status check or reuse a request ID with changed input. A completed job, current saved layout, and successful manufacturing check remain distinct facts.
Private access before signup supports a board's edits, layouts, checks, previews, manufacturing ZIPs, and editable .egb backups without lifetime operation caps or scheduled expiration. Normal request-rate, complexity, and compute protections still apply. The private viewer displays the saved schematic and PCB. Make changes and request exports through the agent; reload the viewer to see saved changes.
Keep the returned private viewer link to return to the board. New exports require current board access; an issued private download link returns its exact exported snapshot without automatic expiry, including after board edits, deletion, claim, or cleanup. Only explicit link revocation or deletion of the exported file ends that download access. The download page refreshes its internal storage authorization automatically. Anyone with a complete private link can use its granted access.
When you connect an account to keep working on the board, the agent calls get_board with the same reference and the service saves it into that personal account with authorized write access. It reads the returned saved state before further edits. No separate claim tool or extra save confirmation is needed. Finish an active layout first; generation polling and stopping do not themselves transfer the board. A busy response calls for waiting, not cancellation or replacement. The account copy preserves the saved layout without copying the old job history; a missing job after transfer is not a reason to regenerate a current layout. Browser sign-in and agent OAuth are separate: the private viewer can save a board after sign-in, but the agent connection still needs its own authorization for account work. Signing in solely for feedback or deletion does not authorize transferring another private board.
Older clients can continue using their existing guestToken, guestCreationKey, and explicit guest-start/claim calls at the compatibility boundary. These are not normal setup steps for new work. Existing credentials remain subject to their original revocation and ownership checks; an expired account connection never silently becomes anonymous.
EasyGerber MCP questions
How do I add EasyGerber MCP to Claude Code?
Run claude mcp add --transport http easygerber-agent-plugin https://www.easygerber.com/api/mcp in your terminal. Add --scope user to make it available in every project.
How do I add EasyGerber MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Do I need to sign up to use EasyGerber?
No, you can search published parts and create a board without signing up using the general MCP connection URL.
Does the MCP server require a local installation of the design engine?
No, the board layout, routing, and scoring run on EasyGerber's hosted servers.