inspect-nextjs-runtime

Diagnose Next.js runtime errors by querying MCP tools to retrieve current build errors, developer logs, and page metadata. This approach maps the project structure and render behavior to accelerate debugging during development.

Map Next.js routes and server actions by inspecting page metadata and route composition through MCP tool queries. This method provides awareness of the app architecture and identifies where structural issues originate across the runtime.

Yes, inspecting Next.js runtime logs requires a running development server. The inspector queries MCP tools against the active runtime to fetch current errors, logs, and metadata to diagnose render behavior and project structure.

Yes, you can compare runtime state across multiple Next.js servers. The inspector uses built-in MCP tools to fetch logs and metadata, helping identify where specific issues originate and understand differences in render behavior.

The next-devtools-mcp package is an optional dependency for high-level guidance. The core runtime inspection queries MCP tools for errors, logs, and metadata, but the package enhances the diagnostic experience for Next.js 16+.

Next.js server actions may render incorrectly due to runtime issues identifiable via MCP tool queries. By retrieving current build errors, developer logs, and page metadata, you can pinpoint structural or behavioral issues causing the failure.