nextjs-devtools

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

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/hafiznaveedchuhan-ctrl/CYBERSECURITY-WORKER-AGENT --skill nextjs-devtools-hafiznaveedchuhan-ctrl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nextjs-devtools
Source: https://github.com/hafiznaveedchuhan-ctrl/CYBERSECURITY-WORKER-AGENT/tree/main/.claude/skills/nextjs-devtools
Command: npx skills add https://github.com/hafiznaveedchuhan-ctrl/CYBERSECURITY-WORKER-AGENT --skill nextjs-devtools-hafiznaveedchuhan-ctrl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Streamlines debugging and exploration of Next.js applications by exposing routes, components, and build information through an MCP server.

Core Features & Use Cases

  • Inspect app routes with list-routes
  • Inspect React components in the Next.js app
  • Retrieve build and configuration info for debugging and optimization
  • Use cases: when debugging routing issues, validating app structure, or auditing builds

Quick Start

Start the MCP server for Next.js devtools and then query it 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 Next.js routes during local development?

To inspect Next.js routes, start the MCP server and run the list-routes command. This exposes your app's routing architecture for local debugging and structural auditing.

Can I retrieve Next.js build information through an MCP server?

Yes, you can retrieve Next.js build and configuration info through an MCP server. Querying the devtools server provides build data for debugging and optimization tasks.

What is the best way to debug Next.js app structure in CI environments?

The best way to debug Next.js app structure in CI is using an MCP-enabled devtools server. It supports on-demand startup to inspect components and routes during automated builds.

Do I need a specific client tool to inspect React components in Next.js?

Yes, you need the nextjs-devtools client tooling and an active MCP server to inspect React components. These components work together to expose app structure for debugging.

How does command-driven tool access work for Next.js debugging?

Command-driven tool access works by querying the MCP server with specific commands like list-routes after on-demand startup. This retrieves targeted architectural insights for Next.js apps.