Next.js DevTools vs hypervibe
Next.js DevTools is an MCP server published by kgprs. Marketplaces we read that list it: 1 (Docker MCP Catalog). hypervibe is a plugin bundle for AI coding tools published by Flavien Chervet. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-26. 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 |  hypervibe |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:3064e349c266 Forks (GitHub): 1 Pulls (Docker Hub): 55 728 Stars (Docker Hub): 0 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Community marketplace flavien-ia/hypervibe-harness | Not listed | Listed Version: 3.4.16 Forks (GitHub): 8 Stars (GitHub): 48 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 | hypervibe |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 7 (worse) | 48 (better) |
| Pulls (Docker Hub) (differs) | 55 728 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 (worse) | 8 (better) |
| Last release (differs) | Not published | 2026-10-23 |
| Where it runs (differs) | On your machine (mcp/next-devtools-mcp) | Remote server (mcp.context7.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 5 | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | Not published | 2 |
| Parts of the bundle (differs) | Not a bundle | 93 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/kgprs/next-devtools-mcp | github.com/flavien-ia/hypervibe-harness |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen (differs) | 2026-10-11 | 2026-10-18 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days 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.
hypervibe
Bootstrap a full-stack T3 project (Next.js + tRPC + Drizzle + Tailwind + shadcn/ui) with modular addons for database, auth, payments, email, storage, i18n, analytics, domain, and SEO. Deploys to Vercel with GitHub integration.
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-mcphypervibe As a Claude Code plugin
/plugin marketplace add flavien-ia/hypervibe-harness
/plugin install hypervibe@hypervibe-harnessCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only hypervibe has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of hypervibe 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: hypervibe · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.