Ext Ops Panel
Open dashboard
Comparison

ucie-wrap vs Sigasi Magic HDL

ucie-wrap is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.

ucie-wrap is a plugin bundle for AI coding tools published by andrewb1999. No marketplace we read lists it any more. Sigasi Magic HDL is an MCP server published by sigasi.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceucie-wrapSigasi Magic HDL
Community marketplace andrewb1999/ucie-wrap-plugin Removed on 2026-10-15
Version: 0.2.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2026092115
Downloads/month (npm): 363
Downloads/week (npm): 63
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

ucie-wrap vs Sigasi Magic HDL
Factucie-wrapno longer listed · Sigasi Magic HDL
Marketplaces that list it (differs)01
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@sigasi/magic-hdl)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/andrewb1999/ucie-wrap-pluginNot stated
Changes in the last 7 days00
First seen (differs)2026-10-142026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of ucie-wrap

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • chip-design-hls

    High-level synthesis — C/C++ to RTL, directive optimization, co-simulation

    by chuanseng-ng · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • xilinx-suite

    An AI coding skill (Claude Code / Codex / OpenClaw) that turns natural language into production-ready Vivado / Vitis HLS / Vitis Unified / PetaLinux scripts. Describe what you…

    by QingquanYao · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • claude-for-hardware

    Skills for hardware design, bring-up, verification, and tapeout

    by Midstall · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • Vivado MCP Native

    Native MCP server for controlling AMD/Xilinx Vivado on Windows and Linux via persistent Tcl.

    by Arthurzxy · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • chip-design-infrastructure

    EDA tool detection, output-filtering shell wrappers, MCP server config templates, and memory distillation for all chip-design domain agents

    by chuanseng-ng · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • chip-design-synthesis

    Logic synthesis — SDC constraints, compile optimization, netlist QC and LEC

    by chuanseng-ng · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

ucie-wrap

In its own words, on Community GitHub marketplaces:

Wrap Vitis HLS AXIS kernels with a verified UCIe FDI die-to-die interface

Sigasi Magic HDL

In its own words, on Official MCP Registry:

Analyze and verify Verilog, SystemVerilog, and VHDL projects from AI agents over MCP.

How to run each

ucie-wrap

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Sigasi Magic HDL As a local MCP server: npm package

Claude Code
claude mcp add --env "MAGIC_HDL_LICENSE_KEY=<YOUR_MAGIC_HDL_LICENSE_KEY>" --transport stdio magic-hdl -- npx -y @sigasi/magic-hdl serve

Requires: MAGIC_HDL_LICENSE_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of ucie-wrap publish no settings it asks for, so we do not compare settings.

What it can do: ucie-wrap · What it can do: Sigasi Magic HDL · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built