Skip to content

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 --doctor

This 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:

  1. EasyEDA Pro is closed: Open EasyEDA Pro and open a project.
  2. Bridge Extension is not installed: Follow the Getting Started Guide to import the .eext file.
  3. 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.
  4. Bridge is not Connected: In the menu bar of EasyEDA Pro, click MCP BridgeConnect. You should see a toast message saying Bridge server connected.
  5. Port conflict or Firewall: The bridge binds to local port 49620 by 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:

  1. Run node -v to check your version.
  2. Use nvm or your platform package manager to update:
    bash
    nvm install 24
    nvm use 24

Released under the MIT License.