Skip to content

AI Client Setup

Use this page when the project is already built and you want the exact setup for one AI tool.

For a first-time flow, start with Quick Start or Getting Started.

Shared Setup

From the repository root:

bash
npm install
npm run setup:local

All clients launch the same local server:

bash
node /absolute/path/to/easyeda_mcp/dist/index.js

Path examples:

text
/Users/you/Documents/easyeda_mcp/dist/index.js
C:\Users\you\Documents\easyeda_mcp\dist\index.js

Choose Your Tool

ToolBest forSetup style
Claude Desktopdesktop chat on Windows or macOSJSON config file
Codex CLIterminal workflow with Codexcodex mcp add
Claude Code CLIterminal workflow with Claudeclaude mcp add or .mcp.json
VS CodeCopilot Chat Agent mode.vscode/mcp.json
Other MCP Clients and CLIsany local stdio MCP clientclient-specific config

Claude Desktop

Use this on Windows or macOS if you want a desktop chat app.

Windows config file:

text
%APPDATA%\Claude\claude_desktop_config.json

macOS config file:

text
~/Library/Application Support/Claude/claude_desktop_config.json

If the file does not exist, create it. Then add one of these examples and replace the path.

macOS example:

json
{
  "mcpServers": {
    "easyeda-pro": {
      "command": "node",
      "args": ["/Users/you/Documents/easyeda_mcp/dist/index.js"]
    }
  }
}

Windows example:

json
{
  "mcpServers": {
    "easyeda-pro": {
      "command": "node",
      "args": ["C:\\Users\\you\\Documents\\easyeda_mcp\\dist\\index.js"]
    }
  }
}

Then:

  1. fully restart Claude Desktop
  2. open EasyEDA Pro
  3. open a schematic or PCB
  4. use MCP Bridge -> Reconnect if needed
  5. ask Claude to run easyeda_doctor

Note: Claude Desktop local MCP setup is separate from Claude.ai remote connectors.

Codex CLI

Use this if you want a terminal workflow in Codex.

bash
codex mcp add easyeda-pro -- node /absolute/path/to/easyeda_mcp/dist/index.js
codex mcp list

Then:

  1. open Codex in this repository
  2. open EasyEDA Pro
  3. open the target schematic or PCB
  4. reconnect the extension if needed
  5. ask Codex to run easyeda_doctor

Claude Code CLI

Use this if you want a terminal workflow in Claude Code.

bash
claude mcp add easyeda-pro -- node /absolute/path/to/easyeda_mcp/dist/index.js
claude mcp list

You can also use a project .mcp.json:

json
{
  "mcpServers": {
    "easyeda-pro": {
      "command": "node",
      "args": ["/absolute/path/to/easyeda_mcp/dist/index.js"]
    }
  }
}

If Claude Desktop is already configured, Claude Code can import from it:

bash
claude mcp add-from-claude-desktop

VS Code

Use this if you want MCP tools in Copilot Chat Agent mode.

Create .vscode/mcp.json:

json
{
  "servers": {
    "easyeda-pro": {
      "type": "stdio",
      "command": "node",
      "args": ["${workspaceFolder}/dist/index.js"]
    }
  }
}

If the VS Code workspace is not the repository root, use an absolute path instead.

Then:

  1. open VS Code in the repository
  2. open Copilot Chat in Agent mode
  3. trust the MCP server when prompted
  4. confirm the server is enabled in the tools picker
  5. ask for easyeda_doctor

Useful VS Code commands:

  • MCP: Open Workspace Folder Configuration
  • MCP: List Servers
  • MCP: Reset Trust

Other MCP Clients and CLIs

If your client supports a local stdio MCP server, use:

bash
node /absolute/path/to/easyeda_mcp/dist/index.js

If the client wants JSON, many MCP clients use this shape:

json
{
  "mcpServers": {
    "easyeda-pro": {
      "command": "node",
      "args": ["/absolute/path/to/easyeda_mcp/dist/index.js"]
    }
  }
}

If the client needs a custom config format, see MCP Client Setup.

After Connecting Any Client

Use the same runtime order for every AI tool:

  1. start the AI tool and let it launch the MCP server
  2. open EasyEDA Pro
  3. open the target schematic or PCB
  4. load or reconnect the EasyEDA Pro extension
  5. run easyeda_doctor

First Useful Prompts

Check health:

text
Run easyeda_doctor and summarize the bridge status.

Confirm the open document:

text
Run easyeda_get_context and tell me which EasyEDA Pro document is open.

Inspect a schematic:

text
Run easyeda_schematic_snapshot and summarize the visible components, nets, and warnings.

Trace a part:

text
Run easyeda_trace_component for USB1 and summarize its connected nets.

Common Problems

  • tools do not appear: rebuild and restart the MCP client
  • tools appear but calls fail: run easyeda_doctor
  • extension is disconnected: open EasyEDA Pro and use MCP Bridge -> Reconnect
  • dist/index.js is missing: run npm run setup:local
  • Windows paths fail in JSON: escape backslashes, for example C:\\Users\\you\\Documents\\easyeda_mcp\\dist\\index.js

Official References

Released under the MIT License. Not affiliated with, endorsed by, or sponsored by EasyEDA or JLCPCB (Shenzhen Jia Chuang Ban Technology Co., Ltd.). EasyEDA and EasyEDA Pro are trademarks of their respective owners.