Troubleshooting
If your AI assistant is unable to communicate with EasyEDA Pro or throws errors, use this guide to identify and fix the issue.
1. Run Diagnostics
The first step is to check if the MCP server is correctly installed and built:
bash
npx easyeda-mcp-pro --doctorThis diagnostic tool checks:
- Node.js runtime version compatibility.
- Presence of built files (
dist/index.js). - Presence of the compiled extension package (
easyeda-bridge-extension.eext). - Availability and reachability of local port
49620.
2. Bridge Connection Issues
If you receive errors like Bridge not connected during tool execution:
Possible Causes:
- EasyEDA Pro is closed: Open EasyEDA Pro and open a project.
- Bridge Extension is not installed: Follow the Getting Started Guide to import the
.eextfile. - Eklenti Devre Dışı / External Interaction is Off: Open the Extension Manager in EasyEDA Pro, select "MCP Pro Bridge", and make sure Allow External Interaction is checked.
- Bridge is not Connected: In the menu bar of EasyEDA Pro, click MCP Bridge → Connect. You should see a toast message saying Bridge server connected.
- Port conflict or Firewall: The bridge binds to local port
49620by default. Ensure no other application is using this port and your firewall allows localhost WebSocket connections.
3. Node.js Version Error
The MCP server relies on modern JavaScript features only available in Node.js version >=24 and <27.
If you see compilation or runtime errors:
- Run
node -vto check your version. - Use
nvmor your platform package manager to update:bashnvm install 24 nvm use 24
