# Next.js DevTools

Next.js DevTools — an MCP server that hands your coding agent Next.js tooling: upgrade guidance, Cache Components setup, and live data from a running dev server.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI
- Author: kgprs
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/kgprs/next-devtools-mcp
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/mcp/nextjs-devtools

## What it does

It runs through `npx` and registers a set of Next.js tools inside the MCP client. From there an agent can take a project through the move to Next.js 16 or switch on Cache Components. A knowledge base for version 16 comes bundled, split into focused resources that load on demand instead of filling the context window.

With `experimental.mcpServer` enabled, the agent also talks to your running dev server. It reads actual routes, compiler diagnostics and error state rather than inferring them from source files. Browser automation goes through Playwright, and prebuilt prompts such as `upgrade-nextjs-16` handle the routine cases.

Node.js v20.19 is the floor, or a newer LTS release, along with npm or pnpm. Anything older will not start the server. On Windows 11, Codex users add `SystemRoot` and `PROGRAMFILES` to `.codex/config.toml` and raise the startup window to `startup_timeout_ms = 20_000`.

## Requirements
- Needs: Docker

## Install

### Claude Code (native platform)

**Install**
- The MCP registry has no launch command for it: see the repository README

## When to use it
- Move a Next.js app to version 16 without guessing the order of steps
- Turn on Cache Components and get `use cache` right
- Read the real route list from a running dev server
- Surface compiler errors without tailing terminal output
- Run a Playwright check against a page

## Example prompts
- Next Devtools, walk me through upgrading this app to Next.js 16
- Next Devtools, what routes does my dev server actually have?
- Next Devtools, show me the compiler errors from the running server

## Similar
- [next-devtools-mcp](https://affpapa.org/en/nevibecode/mcp/next-devtools-mcp.md) — MCP server · ★ 839 repo stars
- [Three.js DevTools MCP](https://affpapa.org/en/nevibecode/mcp/threejs-devtools-mcp.md) — MCP server · ★ 134 repo stars
- [browser-devtools-mcp](https://affpapa.org/en/nevibecode/skills/browser-devtools-mcp.md) — skill · ★ 126 repo stars
- [next-cache-components-optimizer](https://affpapa.org/en/nevibecode/skills/next-cache-components-optimizer.md) — skill · 22000 installs
- [devtools](https://affpapa.org/en/nevibecode/skills/devtools.md) — skill · 8400 installs
- [react-devtools](https://affpapa.org/en/nevibecode/skills/react-devtools.md) — skill · 2700 installs

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
