Ext Ops Panel
Open dashboard
Comparison

plex-ui vs UI Registry

plex-ui is a plugin bundle for AI coding tools published by plex-ui. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). UI Registry is an MCP server published by mrityunjay-tiwari. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-02. 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
Marketplaceplex-uiUI Registry
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.7.1
Downloads/month (npm): 310
Downloads/week (npm): 31
Forks (GitHub): 1
Stars (GitHub): 5
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

plex-ui vs UI Registry
Factplex-uiUI Registry
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)5 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (ui-registry-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/plex-ui/docsgithub.com/mrityunjay-tiwari/ui-registry-mcp
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

plex-ui

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

Teach your AI agent the Plex UI component library — subpath imports, unified size scale (3xs–3xl), semantic colors, dark mode via light-dark, and 460+ icons. Works with 35+ components (Button, Input, Select, Sidebar, Menu, Dialog, Tabs, DatePicker, and more), 14 hooks, and 460+ icon subpath imports. Auto-invokes when your project imports from @plexui/ui.

UI Registry

In its own words, on Official MCP Registry:

Live access to 12 shadcn-style component libraries so agents compose UI from real components.

How to run each

plex-ui As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install plex-ui@claude-community

UI Registry As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio ui-registry-mcp -- npx -y ui-registry-mcp

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

Neither one's marketplaces publish the settings it asks for.

What it can do: plex-ui · What it can do: UI Registry · 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