Next.js DevTools vs UI Registry
Next.js DevTools is an MCP server published by kgprs. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-10-29. 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
| Marketplace |   Next.js DevTools |  UI Registry |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:3064e349c266 Forks (GitHub): 1 Pulls (Docker Hub): 56 064 Stars (Docker Hub): 0 Stars (GitHub): 7 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
| Fact | Next.js DevTools | UI Registry |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 7 (better) | 5 (worse) |
| Pulls (Docker Hub) (differs) | 56 064 | No figure on Docker Hub |
| Forks (GitHub) | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/next-devtools-mcp) | On your machine (ui-registry-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 5 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/kgprs/next-devtools-mcp | github.com/mrityunjay-tiwari/ui-registry-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
Next.js DevTools
next-devtools-mcp is a Model Context Protocol (MCP) server that provides Next.js development tools and utilities for AI coding assistants.
UI Registry
Live access to 12 shadcn-style component libraries so agents compose UI from real components.
How to run each
Next.js DevTools As a local MCP server: Docker image
claude mcp add --transport stdio next-devtools-mcp -- docker run -i --rm mcp/next-devtools-mcpUI Registry As a local MCP server: npm package
claude mcp add --transport stdio ui-registry-mcp -- npx -y ui-registry-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of UI Registry publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Next.js DevTools · What it can do: UI Registry · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.