JLCEDA Codex MCP Bridge
Integrates with JLCPCB/Lichuang EDA Pro (EasyEDA) to export and parse schematic/PCB DRC status, netlists (EasyEDA JSON or Protel2), and BOM (CSV/TSV/XLSX) via a local MCP/HTTP/WebSocket bridge, enabling automated diagnostics, netlist queries, component lookup, and BOM parsing.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@JLCEDA Codex MCP Bridgewhat's the latest export summary?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
JLCEDA Codex MCP Bridge / 嘉立创 EDA Codex MCP 桥接
中文说明
这是一个面向嘉立创 EDA 专业版(JLCPCB/Lichuang EDA Pro)的本地桥接项目。它包含一个嘉立创 EDA 扩展和一个本地 MCP/HTTP/WebSocket 服务,让 Codex 或其他 MCP 客户端可以自动导出并解析:
原理图/PCB DRC 状态
原理图/PCB 网表(EasyEDA JSON 或 Protel2)
BOM(CSV/TSV/XLSX,支持 UTF-16LE/base64)
项目的目标不是替代嘉立创 EDA,而是把 GUI 内部的检查和制造数据变成可程序化读取的 JSON,方便后续做自动诊断、网表查询、BOM 检查和闭环修改。
功能
嘉立创 EDA 顶部菜单:
CodexExport044Live WebSocket 桥接:Codex 可主动请求当前打开工程导出 JSON
一次性 HTTP 导出:扩展可把 JSON 推送到本地服务
MCP 工具:列出导出、请求导出、读取摘要、查询网络、查询器件、解析 BOM、输出诊断
DRC API 调用错误和真实 DRC 条目分离,避免把“当前没有 PCB 画布”误判为设计规则错误
保留原始导出数据,同时提供结构化摘要
目录
extension-live044/ 当前验证过的嘉立创 EDA 扩展源码
mcp/ 本地 MCP server + HTTP/WebSocket bridge
scripts/ 启动、诊断、打包脚本
schemas/ JSON schema
samples/ 脱敏示例导出
tools/ .eext 打包工具默认端口:
HTTP: http://127.0.0.1:38425
WebSocket: ws://127.0.0.1:38426/bridge/ws安装依赖
需要 Node.js 20 或更高版本。
npm install
npm --prefix mcp install启动本地桥接
开发模式:
npm --prefix mcp run httpWindows 后台启动:
.\scripts\start-local-bridge.ps1健康检查:
Invoke-WebRequest -UseBasicParsing http://127.0.0.1:38425/health
Invoke-WebRequest -UseBasicParsing http://127.0.0.1:38425/api/jlceda/ws-status打包嘉立创 EDA 扩展
npm run package:extension生成 .eext 后,在嘉立创 EDA 专业版的扩展管理器中导入。导入并重启嘉立创 EDA 后,打开工程,在顶部菜单点击:
CodexExport044 -> Start Live Bridge连接成功后,Codex/MCP 客户端就可以主动请求导出。
MCP 配置示例
在支持 MCP 的客户端中配置本地 server。把 <repo> 替换为本仓库路径:
{
"mcpServers": {
"jlceda-codex": {
"command": "node",
"args": [
"<repo>\\mcp\\server.js"
],
"env": {
"JLCEDA_EXPORT_DIR": "<repo>\\exports",
"JLCEDA_MCP_HTTP_PORT": "38425",
"JLCEDA_MCP_WS_PORT": "38426"
}
}
}
}Codex config.toml 示例:
[mcp_servers.jlceda_codex]
command = "node"
args = ['<repo>\mcp\server.js']
startup_timeout_sec = 30
[mcp_servers.jlceda_codex.env]
JLCEDA_EXPORT_DIR = '<repo>\exports'
JLCEDA_MCP_HTTP_PORT = "38425"
JLCEDA_MCP_WS_PORT = "38426"MCP 工具
jlceda_list_exports:列出收到的 JSON 导出文件jlceda_bridge_status:查看 live WebSocket 连接状态jlceda_request_export:请求嘉立创 EDA 当前工程立即导出jlceda_latest_export_summary:摘要最新导出jlceda_read_export:读取指定导出 JSONjlceda_parse_protel2_netlist:解析 EasyEDA JSON 或 Protel2 网表jlceda_find_net:查询网络及其连接管脚jlceda_find_component:按位号、值、封装或料号查询器件jlceda_diagnostics:输出 DRC 与未连接管脚诊断jlceda_bom_rows:解析 BOM 行jlceda_export_dir:显示导出目录和端口
验证
npm --prefix mcp run check
npm --prefix mcp run smoke
.\scripts\check-live-bridge.ps1真实闭环验证流程:
启动本地 bridge。
打开嘉立创 EDA 工程。
点击
CodexExport044 -> Start Live Bridge。调用 MCP 工具
jlceda_request_export。用
jlceda_find_net、jlceda_find_component、jlceda_diagnostics分析导出的 JSON。
隐私与限制
exports/、logs/、node_modules/默认不会进入 git。导出的 JSON 可能包含完整网表、BOM、工程路径或器件信息,公开仓库前请不要提交真实项目导出。
嘉立创 EDA 的
SCH_Drc.check和PCB_Drc.check属于 API 中的 BETA 能力,返回结构可能随版本变化。本项目当前实现的是“导出与诊断闭环”的数据通路;自动修改嘉立创工程文件需要额外的编辑策略和复核流程。
License
MIT
Related MCP server: easyeda-mcp
English
This project bridges JLCPCB/Lichuang EDA Pro with Codex and other MCP clients. It includes a JLCEDA Pro extension plus a local MCP/HTTP/WebSocket server that can export and parse:
schematic/PCB DRC status
schematic/PCB netlists, including EasyEDA JSON and Protel2-style data
BOM files, including CSV/TSV/XLSX and UTF-16LE/base64 exports
The goal is not to replace JLCEDA Pro. The goal is to turn GUI-only design checks and manufacturing data into structured JSON that can be queried by automation, reviewed by Codex, and used as the data layer for later closed-loop schematic repair.
Features
JLCEDA Pro top menu:
CodexExport044Live WebSocket bridge: an MCP client can request an export from the currently open project
One-shot HTTP export path from the extension to the local receiver
MCP tools for export listing, live export requests, summaries, net lookup, component lookup, BOM parsing, and diagnostics
DRC API attempt errors are separated from real rule items, so a missing PCB canvas is not reported as a design-rule violation
Raw export payloads are preserved while structured summaries are generated
Repository Layout
extension-live044/ Verified JLCEDA Pro extension source
mcp/ Local MCP server plus HTTP/WebSocket bridge
scripts/ Startup, diagnostics, and packaging scripts
schemas/ JSON schema
samples/ Sanitized sample export
tools/ .eext packaging helperDefault endpoints:
HTTP: http://127.0.0.1:38425
WebSocket: ws://127.0.0.1:38426/bridge/wsInstall
Node.js 20 or newer is required.
npm install
npm --prefix mcp installStart The Local Bridge
Development mode:
npm --prefix mcp run httpHidden Windows background process:
.\scripts\start-local-bridge.ps1Health checks:
Invoke-WebRequest -UseBasicParsing http://127.0.0.1:38425/health
Invoke-WebRequest -UseBasicParsing http://127.0.0.1:38425/api/jlceda/ws-statusPackage And Install The JLCEDA Extension
npm run package:extensionImport the generated .eext file in the JLCEDA Pro extension manager. Restart JLCEDA Pro, open a project, then click:
CodexExport044 -> Start Live BridgeAfter the live bridge is connected, MCP clients can request exports.
MCP Configuration Example
Replace <repo> with the local repository path:
{
"mcpServers": {
"jlceda-codex": {
"command": "node",
"args": [
"<repo>\\mcp\\server.js"
],
"env": {
"JLCEDA_EXPORT_DIR": "<repo>\\exports",
"JLCEDA_MCP_HTTP_PORT": "38425",
"JLCEDA_MCP_WS_PORT": "38426"
}
}
}
}Codex config.toml example:
[mcp_servers.jlceda_codex]
command = "node"
args = ['<repo>\mcp\server.js']
startup_timeout_sec = 30
[mcp_servers.jlceda_codex.env]
JLCEDA_EXPORT_DIR = '<repo>\exports'
JLCEDA_MCP_HTTP_PORT = "38425"
JLCEDA_MCP_WS_PORT = "38426"MCP Tools
jlceda_list_exports: list received JSON exportsjlceda_bridge_status: show live WebSocket statusjlceda_request_export: request a live export from JLCEDA Projlceda_latest_export_summary: summarize the newest exportjlceda_read_export: read a specific export JSONjlceda_parse_protel2_netlist: parse EasyEDA JSON or Protel2 netlistsjlceda_find_net: find a net and connected component pinsjlceda_find_component: find a component by designator, value, footprint, supplier part, or manufacturer partjlceda_diagnostics: return DRC state and unconnected-pin diagnosticsjlceda_bom_rows: return parsed BOM rowsjlceda_export_dir: show the active export directory and bridge ports
Validation
npm --prefix mcp run check
npm --prefix mcp run smoke
.\scripts\check-live-bridge.ps1Real closed-loop test:
Start the local bridge.
Open a project in JLCEDA Pro.
Click
CodexExport044 -> Start Live Bridge.Call
jlceda_request_export.Use
jlceda_find_net,jlceda_find_component, andjlceda_diagnosticsto inspect the exported JSON.
Privacy And Limits
exports/,logs/, andnode_modules/are ignored by git.Exported JSON can contain full netlists, BOMs, project paths, and component data. Do not commit real project exports to a public repository.
JLCEDA
SCH_Drc.checkandPCB_Drc.checkare BETA APIs and their return shape may change.This project provides the export and diagnostics data path. Automatic project-file edits require a separate editing strategy and manual review loop.
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Dissipative-ATLAS/jlceda-codex-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server