Next.js DevTools vs Designesy
Next.js DevTools is an MCP server published by kgprs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Designesy is an MCP server published by LE-VAI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  Designesy |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:3064e349c266 Forks (GitHub): 1 Pulls (Docker Hub): 54 900 Stars (Docker Hub): 0 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.13.9 Downloads/month (PyPI): 741 Downloads/week (PyPI): 1 068 Forks (GitHub): 0 Stars (GitHub): 0 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 | Designesy |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 7 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 54 900 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | On your machine (mcp/next-devtools-mcp) | Remote server (www.designesy.org/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| 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/le-vai/designesy-org |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 12 h ago |
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.
Designesy
Design quality gate for AI-generated UI: score any URL on 45 deterministic checks, A–F grade.
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-mcpDesignesy As a remote MCP server
claude mcp add --transport http designesy-org https://www.designesy.org/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Designesy has a remote endpoint we check. How we check endpoints
Tools each declares
Only Next.js DevTools has
browser_evalenable_cache_componentsnextjs_docsnextjs_runtimeupgrade_nextjs_16
Only Designesy has
designesy_a11y_scoredesignesy_agent_jsondesignesy_catalogdesignesy_comparedesignesy_contractdesignesy_design_reviewdesignesy_drift_scoredesignesy_guardrailsdesignesy_llms_full_txtdesignesy_llms_txtdesignesy_monitor_scoredesignesy_motion_score
Show the remaining 5
designesy_readiness_scoredesignesy_reportdesignesy_scoredesignesy_skill_mddesignesy_tokens_score
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Designesy as of 2026-10-16). More tools is not better in itself: compare what each needs for the job.
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: Designesy · 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.