Skip to main content
Glama
0xruth1ezz

JLC EDA MCP Server

by 0xruth1ezz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to JLC EDA MCP Server

No user-submitted related servers found.

    Related Servers

    • easyeda-mcp

      cheewee2000
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients like Claude Code to control a running EasyEDA Pro instance for PCB design automation, including DRC checks, project management, and script execution via a bridge server.
      5 npm
      MIT

    • 果子狸MCP服务

      lyq11
      F
      license
      B
      quality
      B
      maintenance
      Connects Jia Li Chuang EDA / EasyEDA Pro schematics to MCP clients, enabling AI-driven schematic editing, reading, and analysis.
      19
      -

    • jlceda-ai-agent

      jiangyiqi99
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to automate 嘉立创 EDA Professional through MCP, including schematic and PCB editing, component search and placement, net routing, DRC, and design capture.
      -

    • a2n-easyeda-mcp

      anwarminarso
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to control EasyEDA Pro for schematic and PCB design through natural language, bridging the EasyEDA API without external AI or API keys.
      49
      MIT

    • jlceda-mcp

      qcz2943
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with 嘉立创 EDA for PCB design tasks including project management, component libraries, rule checking, and manufacturing constraints.
      14 npm
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 38 tools

    Disambiguation5/5

    Each tool targets a specific operation (create, delete, get, move, etc.) on a distinct object (component, track, via, etc.). The prefixes pcb_, sch_, calc_ further separate domains. Even similar operations like delete are differentiated by object type, and move vs relocate have distinct behaviors.

    Naming Consistency5/5

    All tools follow a consistent pattern of domain prefix (pcb_, sch_, calc_) followed by verb_noun (e.g., pcb_create_component, pcb_get_board_info). No mixing of styles, and verbs are consistently placed.

    Tool Count4/5

    With 38 tools, the set is comprehensive for PCB and schematic design automation but slightly high. Most tools are necessary for common workflows, though some redundancy exists (e.g., multiple delete tools) that could be consolidated.

    Completeness3/5

    The PCB tool surface is fairly complete with creation, deletion, querying, and routing. However, schematic tools are limited to three read/export functions, missing creation or editing. Also, some PCB operations like editing component properties or board outline tools are absent.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources