Sigasi Magic HDL
com.sigasiPublished by sigasi.comv0.1.2026092115Updated Oct 24, 2026
Analyze and verify Verilog, SystemVerilog, and VHDL projects from AI agents over MCP.
Overview
A local MCP server that lets an AI assistant analyze and verify Verilog, SystemVerilog and VHDL hardware-design projects.
- What you can do
- Analyze Verilog, SystemVerilog and VHDL projects from an AI agent over MCP, so the assistant can inspect hardware-design code in place rather than guessing from pasted snippets. Verification of those projects is the stated purpose; the manifest lists no individual tools, so the exact operations are not documented here. It runs as a local process on the user's own machine, working against the project files there.
- When to use it
- Worth adding when an assistant is helping with FPGA or ASIC design work in Verilog, SystemVerilog or VHDL and needs to analyze or verify the actual project rather than reason about code in isolation. It is a desktop-only tool, so it suits local development machines.
- Requirements
- Runs locally over stdio, launched with npx from the npm package @sigasi/magic-hdl, so Node.js and network access for the package are needed. A Magic HDL license key is supplied through the MAGIC_HDL_LICENSE_KEY environment variable, but only when the machine has no stored key yet; the documented setup path is the magic-hdl login and magic-hdl setup commands.
Installation
In SourceWeft
- Open Sigasi Magic HDL in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Tools
0Version history
2- v0.1.2026092115LatestSep 22, 2026
- v0.1.2026091708Sep 17, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.