Next.js DevTools MCP
Connects an agent to a running Next.js dev server so it can read routes, build output, and runtime errors instead of guessing from source alone.
What it does
Connects an agent to a running Next.js dev server so it can read routes, build output, and runtime errors instead of guessing from source alone. Useful during a refactor when the failure only appears at render time. It talks to a local server, so it is a development tool — do not ship it to anything public.
Install
npx -y next-devtools-mcp
Client configuration
Paste this into your MCP client config (Claude Desktop, Cursor, or any client that reads mcpServers), then restart the client.
{
"mcpServers": {
"next-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp"
]
}
}
}
When to use it
Reach for this when the task needs nextjs inside the agent loop. Skip it if a plain shell command or a one-off script is enough — every server you add costs context and adds a failure mode.
Other TypeScript servers
- Filesystem — Gives an agent scoped read, write, and search access to directories you explicitly allow
- Memory — A persistent knowledge graph stored in a local JSON file, exposed through entities, relations, and observations
- Sequential Thinking — Gives the model a scratchpad for structured, revisable reasoning: numbered thoughts that can branch, revise, and conclude