Nextjs devtools

Skill bg-szy/TOP-SKILLS/skills/marketplace/nextjs-devtools

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install

npx -y skills add bg-szy/TOP-SKILLS --skill nextjs-devtools

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Next.js development tooling via MCP. Inspect routes, components, build info, and debug Next.js apps. Use when working on Next.js applications, debugging routing, or inspecting app structure. NOT for general React or non-Next.js projects.

SKILL.md

2.2 KB, 547 tokens by cl100k_base, as published. Nobody here has run it

Next.js DevTools

Inspect and debug Next.js applications via MCP server.

Quick Start

# Start server (spawns on-demand)
bash scripts/start-server.sh

# Or use directly via mcp-client
python3 scripts/mcp-client.py call \
  -s "npx next-devtools-mcp@latest" \
  -t list-routes

Available Tools

Tool	Description
`list-routes`	Get all app routes
`get-route-info`	Details for specific route
`list-components`	React components in app
`get-build-info`	Build configuration
`get-config`	next.config.js settings

Workflow Patterns

Pattern 1: Route Inspection

# List all routes
python3 scripts/mcp-client.py call \
  -s "npx next-devtools-mcp@latest" \
  -t list-routes

# Get specific route details
python3 scripts/mcp-client.py call \
  -s "npx next-devtools-mcp@latest" \
  -t get-route-info \
  -p '{"route": "/api/auth"}'

Pattern 2: Debug Build Issues

# Check build config
python3 scripts/mcp-client.py call \
  -s "npx next-devtools-mcp@latest" \
  -t get-build-info

# Check next.config.js
python3 scripts/mcp-client.py call \
  -s "npx next-devtools-mcp@latest" \
  -t get-config

Pattern 3: Component Discovery

python3 scripts/mcp-client.py call \
  -s "npx next-devtools-mcp@latest" \
  -t list-components

Scripts

start-server.sh

For persistent server (multiple calls):

bash scripts/start-server.sh
# Server runs on default port
# Use mcp-client.py with -u flag instead of -s

On-Demand (Recommended)

For single calls, use -s flag which spawns server per-call:

python3 scripts/mcp-client.py call \
  -s "npx next-devtools-mcp@latest" \
  -t <tool-name>

Troubleshooting

Issue	Solution
Server not starting	Check `npx next-devtools-mcp@latest` works manually
No routes found	Ensure running from Next.js project root
Build info empty	Run `next build` first

What ships with it: 1 file

57.4 KB alongside SKILL.md

skill-report.json57.4 KB

Gives 0 of the 12 instructions most debug triage skills give in 547 tokens

Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-07

Investigate root cause before proposing any fixin 102 of 839, across 67 files
Read error messages completelyin 89 of 839, across 49 files
Create a failing test case before fixingin 84 of 839, across 46 files
Reproduce the issue consistentlyin 82 of 839, across 41 files
Change one variable at a timein 82 of 839, across 42 files
Check recent changesin 74 of 839, across 36 files
Write the regression test before fixingin 74 of 839, across 40 files
Fix the root cause not the symptomin 60 of 839, across 45 files
Implement a single fix at a timein 59 of 839, across 20 files
Trace data flow backward to the sourcein 50 of 839, across 20 files
Remove all debug instrumentationin 49 of 839, across 13 files
Form a single hypothesisin 48 of 839, across 18 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.