Skip to main content
Glama
hslee-cmyk

Xcelium MCP Server

by hslee-cmyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Xcelium MCP Server

No user-submitted related servers found.

    Related Servers

    • rtl-mcp-agent

      cbfaf
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to analyze RTL simulation and synthesis logs through deterministic tools for compile-log summaries, signal tie-off safety checks, and regression result statistics.
      -

    • visualizer-mcp

      htminuslab
      A
      license
      A
      quality
      D
      maintenance
      Connects AI assistants to Siemens Questa Visualizer, enabling natural language control of HDL simulation such as opening waveforms, running simulation, and examining signal values.
      12
      2
      MIT

    • Verilator MCP Server

      ssql2014
      A
      license
      C
      quality
      F
      maintenance
      Enables RTL simulation and hardware verification with Verilator through automatic testbench generation, natural language queries about simulations, waveform analysis, and protocol-aware testing for Verilog/SystemVerilog designs.
      4
      4
      MIT

    • mcp-verilog

      zesun33
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents and IDEs to lint, compile, syntax-check, and simulate Verilog/SystemVerilog designs through structured, token-efficient MCP tools with isolated containerized toolchains.
      4
      17 npm
      Apache 2.0
    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.4/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., deposit_value vs. release_signal, save_checkpoint vs. restore_checkpoint). Minor potential confusion exists between disconnect_simulator and shutdown_simulator (both end sessions but differ in data preservation), and between watch_signal and bisect_signal (both detect conditions but via different mechanisms). Descriptions clarify these distinctions.

    Naming Consistency4/5

    Generally follows verb_noun convention (e.g., connect_simulator, set_breakpoint, find_drivers). Consistent prefixes group related functionality (sim_*, watch_*, waveform_*). Minor deviations include cursor_set (noun_verb inversion compared to set_breakpoint) and run_debugger_mode (slightly vague compared to specific action names).

    Tool Count3/5

    With 25 tools, this is at the upper boundary of the 16-25 range, feeling heavy for an MCP server. While the hardware simulation domain is complex and justifies extensive coverage (signals, checkpoints, waveforms, debugging), the surface area is large enough that an agent may struggle to select the optimal tool without careful description reading.

    Completeness4/5

    Provides comprehensive coverage for hardware debugging workflows: connection lifecycle, simulation control (run/stop/restart), signal inspection/manipulation, checkpoint management, conditional breakpoints/watchpoints, and waveform visualization. Minor gaps include lack of explicit 'step' (single-cycle advance) or direct Tcl command execution, though set_breakpoint allows Tcl expressions.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources