Ext Ops Panel
Open dashboard
Comparison

rtl-agent-team vs io.neosyn/cg-agent-kit

rtl-agent-team is a plugin bundle for AI coding tools published by babyworm. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.neosyn/cg-agent-kit is an MCP server published by neosyn.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacertl-agent-teamio.neosyn/cg-agent-kit
Community marketplace babyworm/rtl-agent-team Listed
Version: 0.14.6
Forks (GitHub): 16
Stars (GitHub): 67
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed, marked deprecated
Version: 0.2.1
Downloads/month (PyPI): 188
Downloads/week (PyPI): 10
Forks (GitHub): 1
Stars (GitHub): 1
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

rtl-agent-team vs io.neosyn/cg-agent-kit
Factrtl-agent-teamio.neosyn/cg-agent-kit
Marketplaces that list it11
Stars (GitHub) (differs)67 (better)1 (worse)
Forks (GitHub) (differs)16 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (cg-agent-kit)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Hooks it runs (differs)15Not published
Parts of the bundle (differs)202Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/babyworm/rtl-agent-teamgithub.com/neosyn-logic/cg-agent-kit
Changes in the last 7 days00
First seen (differs)2026-10-152026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

rtl-agent-team

In its own words, on Community GitHub marketplaces:

99-agent RTL design pipeline with 97 skills for 6-Phase hardware design automation (Research → Architecture → μArch → RTL → Verify → Design Note)

io.neosyn/cg-agent-kit

In its own words, on Official MCP Registry:

AI-agent MCP server for FPGA design: compile, validate & generate Verilog from C⏚ HDL.

How to run each

rtl-agent-team As a Claude Code plugin

Claude Code
/plugin marketplace add babyworm/rtl-agent-team
/plugin install rtl-agent-team@rtl-agent-marketplace

io.neosyn/cg-agent-kit As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio cg-agent-kit -- uvx cg-agent-kit

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 rtl-agent-team publish no settings it asks for, so we do not compare settings.

What it can do: rtl-agent-team · What it can do: io.neosyn/cg-agent-kit · 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