Next.js 16+ can expose a built-in MCP endpoint from the dev server (typically /_next/mcp). The next-devtools-mcp connector discovers running servers and gives agents live runtime diagnostics instead of guessing from static HTML.
When to use
Debugging hydration, Server Actions, or route errors while next dev is running
Inspecting routes, logs, and framework tooling with evidence from the live app
Pointing agents at version-matched docs under node_modules/next/dist/docs/
Context7 MCP for library docs outside the Next package
Raw content
Copy into your project — e.g. .instructions.md, .agent.md, or SKILL.md
## Overview
Next.js 16+ can expose a built-in MCP endpoint from the dev server (typically `/_next/mcp`). The `next-devtools-mcp` connector discovers running servers and gives agents live runtime diagnostics instead of guessing from static HTML.
## When to use
- Debugging hydration, Server Actions, or route errors while `next dev` is running
- Inspecting routes, logs, and framework tooling with evidence from the live app
- Pointing agents at version-matched docs under `node_modules/next/dist/docs/`
## Setup
1. Run your Next.js 16+ app with `next dev`
2. Install and configure upstream `next-devtools-mcp` per https://github.com/vercel/next-devtools-mcp
3. Prefer this MCP (plus bundled Next docs) over outdated training-data Next 13/14 patterns
## Related
- [Neexo Next.js Conventions](/instructions/nextjs-conventions)
- [Context7 MCP](/tools/context7-mcp) for library docs outside the Next package