nextjs-devtools

Inspect Next.js routes, components, and build configuration via MCP.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Razaib-khan/Hackathon-2-phases-2-3-4-5- --skill nextjs-devtools-razaib-khan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nextjs-devtools
Source: https://github.com/Razaib-khan/Hackathon-2-phases-2-3-4-5-/tree/main/.claude/skills/nextjs-devtools
Command: npx skills add https://github.com/Razaib-khan/Hackathon-2-phases-2-3-4-5- --skill nextjs-devtools-razaib-khan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you inspect and debug Next.js applications without guessing, making it easier to understand routes, components, build configuration, and app structure during development.

Core Features & Use Cases

  • Route Inspection: List application routes and retrieve details for a specific page or API path.
  • Component Discovery: Identify React components used in the app to speed up navigation and debugging.
  • Build and Config Review: Check build information and Next.js configuration when diagnosing deployment or runtime issues.
  • Use Case: If a page is failing or a route behaves unexpectedly, use this Skill to quickly inspect the app structure and locate the relevant implementation details.

Quick Start

Ask the Skill to inspect the Next.js app routes and identify the component or config details related to the issue you are debugging.

Frequently Asked Questions about nextjs-devtools

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inspect Next.js app routes and components during debugging?

To inspect Next.js app routes and components, you can query the application structure deterministically using the bundled MCP client and Next DevTools server, listing routes and identifying React components to speed up navigation and debugging.

What is the best way to diagnose unexpected Next.js page routing behavior?

Diagnosing unexpected Next.js page routing behavior involves inspecting the app structure to locate relevant implementation details and retrieving specific page or API path data without guessing the route configuration.

Can I check Next.js build configuration and details for runtime issues?

Yes, you can check Next.js build information and configuration to diagnose deployment or runtime issues, retrieving build metadata deterministically through the MCP client and DevTools server.

Does this Next.js inspection approach work with API routes?

Yes, this Next.js inspection approach works with API routes, applying to development workflows involving API route inspection, page routing, component discovery, and configuration troubleshooting via the DevTools server.

Do I need an MCP client to inspect Next.js application structure?

Yes, you need MCP access through the bundled client and Next DevTools server to query app metadata deterministically and inspect the Next.js application structure, routes, and components.