tla-claude-code vs Sigasi Magic HDL
tla-claude-code is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
tla-claude-code is a plugin bundle for AI coding tools published by brianwu02. 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-26. 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
| Marketplace |  Sigasi Magic HDL | |
|---|---|---|
| Community marketplace brianwu02/tla-claude-code | Removed on 2026-10-17 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.2026092115 Downloads/month (npm): 834 Downloads/week (npm): 52 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
| Fact | tla-claude-codeno longer listed · | Sigasi Magic HDL |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@sigasi/magic-hdl) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/brianwu02/tla-claude-code | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-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 tla-claude-code
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Systematically debug issues with step-by-step troubleshooting approaches.
-
Unified toolkit for Context-Driven Development with spec-first planning, TDD workflow, and OKF knowledge bundles.
-
Prevent, catch, and verify architectural violations while Claude Code works.
-
AI code review that catches production-breaking bugs, business logic issues, and security vulnerabilities — directly in Claude Code.
-
Description: Adversarial code hardening for Claude Code. Forge spawns two agents — a Builder and a Breaker — that iterate against each other until the code is unbreakable. The…
-
SOLID principles enforcement with automatic project detection and validation for all languages
What each says it does
tla-claude-code
TLA+ formal verification for concurrency bugs, race conditions, and UX flow issues
Sigasi Magic HDL
Analyze and verify Verilog, SystemVerilog, and VHDL projects from AI agents over MCP.
How to run each
tla-claude-code
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 mcp add --env "MAGIC_HDL_LICENSE_KEY=<YOUR_MAGIC_HDL_LICENSE_KEY>" --transport stdio magic-hdl -- npx -y @sigasi/magic-hdl serveRequires: 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 tla-claude-code publish no settings it asks for, so we do not compare settings.
What it can do: tla-claude-code · 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.