Ext Ops Panel
Open dashboard
Comparison

rootcx vs io.github.mwbidwell/bionicforms-mcp

rootcx is a plugin bundle for AI coding tools published by RootCX. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.mwbidwell/bionicforms-mcp is an MCP server published by mwbidwell. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
Marketplacerootcxio.github.mwbidwell/bionicforms-mcp
Claude Code: claude-plugins-community Listed
Version: 0.2.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed, marked deprecated
Version: 1.0.3
Downloads/month (npm): 147
Downloads/week (npm): 18
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

rootcx vs io.github.mwbidwell/bionicforms-mcp
Factrootcxio.github.mwbidwell/bionicforms-mcp
Marketplaces that list it11
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 (@bionicforms/mcp-server)
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)9Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/rootcx/claude-code-plugingithub.com/mwbidwell/form_builder
Changes in the last 7 days00
First seen2026-10-112026-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

rootcx

In its own words, on Claude Code: claude-plugins-community:

Official plugin for RootCX, the open-source platform for building internal software and AI agents on a unified, secure foundation. Connect to any RootCX Core, scaffold apps and agents, and deploy from Claude Code. Enterprise SSO, RBAC, audit logs, and managed PostgreSQL are built in. Develop locally, deploy anywhere.

io.github.mwbidwell/bionicforms-mcp

In its own words, on Official MCP Registry:

Build forms, manage responses, and run AI analysis via the BionicForms API.

How to run each

rootcx

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

io.github.mwbidwell/bionicforms-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "BIONICFORMS_API_KEY=<YOUR_BIONICFORMS_API_KEY>" --transport stdio bionicforms-mcp -- npx -y @bionicforms/mcp-server

Requires: BIONICFORMS_API_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 rootcx publish no settings it asks for, so we do not compare settings.

What it can do: rootcx · What it can do: io.github.mwbidwell/bionicforms-mcp · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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