What it does
This MCP server integrates with Next.js development environments (version 16 and later) to expose runtime diagnostics and development tools. It connects to a running Next.js app's internal MCP endpoint, reads project files, and provides tools to query the application's actual runtime state—including route structure, error logs, and diagnostic data. The server also surfaces Next.js official documentation and automation helpers for version upgrades and feature enablement.
Who it's for
Backend and fullstack engineers building Next.js applications who want AI-assisted exploration and debugging of their running applications. Teams seeking automated help with version migrations, feature adoption, and understanding complex application architecture without manual inspection.
Common use cases
- Query runtime errors and diagnostics from a running Next.js 16+ dev server
- Explore application route structure and component relationships via the
nextjs_indextool - Search Next.js official documentation for API details and implementation patterns
- Automate Next.js version upgrades or feature enablement across a codebase
- Review development server logs for debugging and troubleshooting
Setup pitfalls
- Requires Node.js v20.19 or a newer LTS version
- Next.js 16+ projects must have the dev server running at the expected port for runtime diagnostics to function
- The
inittool must be called first to establish proper MCP context before using other tools - Reads and writes filesystem access is required; ensure appropriate sandbox and permission settings in your coding agent's configuration