multiAI Summary Pending
nextjs-devtools
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.
231 stars
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/nextjs-devtools/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/92bilal26/nextjs-devtools/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/nextjs-devtools/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How nextjs-devtools Compares
| Feature / Agent | nextjs-devtools | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Next.js DevTools
Inspect and debug Next.js applications via MCP server.
## Quick Start
```bash
# 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
```bash
# 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
```bash
# 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
```bash
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
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:
```bash
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 |