Verilator MCP Server
Related Servers
Alternatives to Verilator MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables 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.417 npmApache 2.0
- FlicenseAqualityDmaintenanceEnables AI assistants to perform Electronic Design Automation (EDA) tasks including Verilog synthesis, simulation, ASIC design flows, and waveform analysis through a unified interface.6-
- AlicenseBqualityBmaintenanceEnables AI assistants to control Cadence Xcelium and SimVision simulators in real time for automated RTL and gate-level debugging. It provides 25 tools for signal inspection, watchpoints, binary search, and simulation state management.251MIT
- FlicenseNot gradedqualityBmaintenanceEnables LLMs to interact with hardware designs (Verilog/SystemVerilog), formal verification tools, waveform logs, protocol specifications, and bug databases through 34 structured tools.-
- AlicenseNot gradedqualityDmaintenanceEnables analysis of RTL waveform files (VCD, FST) through WAL (Waveform Analysis Language). Supports signal inspection, transition extraction, and advanced waveform queries for hardware design verification.16BSD 3-Clause
- AlicenseAqualityBmaintenanceEnables AI coding agents and IDEs to perform AST-backed semantic Verilog/SystemVerilog code reviews, catching race conditions, reset polarity mismatches, and bitwidth truncations while computing a 0–100 RTL quality score.416 npmApache 2.0
TDQS
Scored across 4 tools
The tools have distinct primary purposes: compile, simulate, generate testbenches, and handle natural language. However, 'verilator_simulate' can auto-generate testbenches if needed, overlapping with 'verilator_testbenchgenerator', which could be confusing for an agent deciding which tool to use for testbench creation.
All tool names follow the verb_noun pattern (e.g., verilator_compile, verilator_simulate), with 'verilator_' as a consistent prefix. The only deviation is 'verilator_testbenchgenerator' and 'verilator_naturallanguage' which combine two words without a separator, but the pattern is still readable.
With 4 tools, the count is on the low end but appropriate for a focused server covering compilation, simulation, testbench generation, and natural language processing. It feels slightly thin for a full RTL workflow but each tool earns its place.
The server provides essential compile and simulate operations but lacks tools for waveform viewing (e.g., VCD/FSDB dumping), coverage analysis, or linting/static checks. There is a 'natural language' tool for analysis, but concrete operations like setting simulation timeouts, reading simulation results, or writing traces are missing, creating significant gaps for debugging workflows.