Midnight + Next.js MCP vs io.github.vercel/next-devtools-mcp
Midnight + Next.js MCP is an MCP server published by FractionEstate. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.vercel/next-devtools-mcp is an MCP server published by vercel. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 |  Midnight + Next.js MCP |  io.github.vercel/next-devtools-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.1 Downloads/month (npm): 206 Downloads/week (npm): 27 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.3.6 Downloads/month (npm): 472 323 Downloads/week (npm): 67 187 Forks (GitHub): 66 Stars (GitHub): 832 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 | Midnight + Next.js MCP | io.github.vercel/next-devtools-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 832 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 66 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (midnight-nextjs-mcp) | On your machine (next-devtools-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/fractionestate/midnight-nextjs-mcp | github.com/vercel/next-devtools-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
Midnight + Next.js MCP
Unified MCP server for Midnight blockchain development and Next.js dApps.
io.github.vercel/next-devtools-mcp
Next.js development tools MCP server with stdio transport
How to run each
Midnight + Next.js MCP As a local MCP server: npm package
claude mcp add --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --transport stdio midnight-nextjs-mcp -- npx -y --experimental-vm-modules midnight-nextjs-mcpRequires: GITHUB_TOKEN (secret)
io.github.vercel/next-devtools-mcp As a local MCP server: npm package
claude mcp add --transport stdio next-devtools-mcp -- npx -y next-devtools-mcpCommands 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 io.github.vercel/next-devtools-mcp publish no settings it asks for, so we do not compare settings.
What it can do: Midnight + Next.js MCP · What it can do: io.github.vercel/next-devtools-mcp · Compare two other plugins
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.