nextjs-devtools

Inspect Next.js routes, components, and build info via MCP server.

9|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/AbdullahMalik17/My_skills --skill nextjs-devtools-abdullahmalik17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nextjs-devtools
Source: https://github.com/AbdullahMalik17/My_skills/tree/main/.claude/skills/nextjs-devtools
Command: npx skills add https://github.com/AbdullahMalik17/My_skills --skill nextjs-devtools-abdullahmalik17

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Next.js developers often need quick insight into app structure, routes, and build configuration without leaving their development environment.

Core Features & Use Cases

  • Inspect routes, components, and build info for Next.js apps via MCP.
  • Debug routing issues and understand app structure across multiple projects.
  • Use Case: When diagnosing a failing API route, list routes, view route details, and inspect component usage to pinpoint the issue.

Quick Start

Start the MCP-backed server and use the MCP client to query routes, components, and build info for your current Next.js project. Example: start the server and run a query to list routes.

Frequently Asked Questions about nextjs-devtools

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

FAQPage Schema
How do I inspect routes and components in my Next.js app without leaving my development environment?

Inspect routes, components, and build info directly via MCP by starting the next-devtools-mcp server and querying your Next.js project workspace. This provides immediate visibility into app structure and routing configuration for debugging without external tools.

Can I debug Next.js routing issues by listing all routes and viewing route details?

Yes. List routes and inspect route details through the MCP interface to diagnose routing failures. View component usage across routes to pinpoint structural issues causing API route or page failures.

What do I need to start debugging a Next.js app with devtools?

You need Node.js/npm, the next-devtools-mcp MCP tool installed, and access to your Next.js project workspace. The Skill automates inspection by interfacing with the MCP server to surface routes, components, and build configuration.

How do I understand my Next.js app structure across multiple projects?

Use the MCP-backed devtools to query and compare routes, components, and build info across projects. This surfaces architectural patterns and identifies structural inconsistencies without manual code review.

What's the fastest way to diagnose why an API route is failing in Next.js?

List all routes via MCP, view the failing route's details, and inspect component usage to identify the root cause. The Skill surfaces routing and structural issues directly for rapid diagnosis.