Skip to main content
Glama
Sign In
efinity-mcp

efinity-mcp

by shubhamdraveriya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to efinity-mcp

No user-submitted related servers found.

    Related Servers

    • fpga-mcp

      wmm246
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to drive Xilinx Vivado, Intel Quartus, and Anlogic TangDynasty for FPGA development, including project creation, synthesis, implementation, timing closure, and hardware programming through natural language.
      37 PyPI
      6
      MIT

    • Vivado MCP

      binghin2
      A
      license
      B
      quality
      C
      maintenance
      Enables AI coding assistants to drive Xilinx Vivado through natural language, letting users open .xpr projects, run synthesis, implementation, and bitstream generation, inspect timing, resource, and clock reports, and launch simulations to read signal values or set breakpoints. It also exposes design hierarchy queries and arbitrary TCL execution, so FPGA design flows can be operated conversationally on Windows.
      40
      MIT

    • mcp-fpga

      zesun33
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents and IDEs to run a complete open-source FPGA flow, including synthesis, place-and-route, bitstream generation, and safe hardware programming for iCE40/ECP5 boards.
      6
      11 npm
      Apache 2.0

    • vivado-mcp

      andersfontana
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents such as Claude Code, Cursor, and Codex to drive a locally installed Xilinx Vivado through 32 curated tools covering sessions, synthesis, implementation, timing and CDC reports, XDC, IP, waveforms, and device programming. It also provides structured timing evidence with baseline comparison, offline VCD queries, environment self-diagnostics, and evidence-driven workflow prompts.
      -

    • vivado-mcp

      YuiSchmidt870
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents such as Claude Code, Cursor, and Codex to drive a locally installed Xilinx Vivado across the full FPGA flow, from GUI, headless Tcl, or attached sessions through synthesis, implementation, timing and CDC analysis, waveform queries, and device programming. It exposes 32 curated tools plus evidence-driven workflow prompts that return structured timing/IO reports, Chinese-language CRITICAL WARNING diagnostics, and guarded bitstream generation.
      -

    • vivado-mcp

      SaraRao6460
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents such as Claude Code, Cursor, and Codex to drive a locally installed Xilinx Vivado across the full FPGA flow, with tools for sessions, synthesis, implementation, timing, CDC, XDC, IP, waveform querying, and device programming. It also provides structured timing evidence with baseline comparison, offline VCD analysis, evidence-driven workflow prompts, and a read-only doctor for environment self-checks.
      -
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.8/5.0

    Scored across 27 tools

    Disambiguation4/5

    Tool purposes are mostly distinct, and the descriptions clearly separate enumerations from details, reports from actions, and summary views from specialized queries. The main overlap risk is between get_build_status and the specialized timing/utilization/messages tools, and between get_interface_design's optional check and check_interface, but these are not severe.

    Naming Consistency5/5

    All tools use lowercase snake_case with a consistent verb-first pattern: list_* for enumerations, get_* for entities and status, create_/update_ for project mutations, and run_/check_/calc_/export_/program_ for actions. There are no camelCase or mixed-convention names.

    Tool Count4/5

    27 tools is on the heavier side, but the server covers a broad FPGA lifecycle: project management, interface design, build flow, timing analysis, reporting, and programming. Each tool has a defined role, and while a few reporting tools could be consolidated, the count is defensible for the domain.

    Completeness4/5

    The lifecycle is well covered: project create/update/read, Interface Designer editing/checking/export, flow execution and job monitoring, timing and STA analysis, report access, and device programming. Minor gaps such as no project deletion or direct SDC editing are workable and do not create dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Resources