Next.js DevTools, verificado
Servidor MCP de Vercel · Verificado
Query a running Next.js dev server for runtime errors, routes and logs, and find version-matched docs from your coding agent.
Instalar Next.js DevTools
Se ejecuta en tu equipo. Tu cliente lo inicia con este comando:
Requiere Node.js en tu equipo. Los pasos de configuración de abajo muestran dónde va el comando en cada cliente.
Compartir este servidor
Abre esta página, con el comando de instalación y los pasos de configuración.
mcp.tc/i/nextjs-devtoolsDescripción
Connects coding agents such as Claude Code and Cursor to a running Next.js 16+ dev server. It discovers local dev servers, proxies their built-in MCP endpoint (/_next/mcp) and returns live build and runtime errors, routes, page metadata, project config and dev logs. Two gateway tools point the agent at the docs bundled in node_modules/next/dist/docs and at the agent-browser CLI for browser automation.
Runs locally over stdio with npx -y next-devtools-mcp@latest. Requires Node.js 20.19 or newer and, for the runtime tools, a Next.js 16+ dev server started with npm run dev. No sign-in or API key is needed.
Qué puedes hacer
- Discover running Next.js dev servers and list their runtime tools
- Read current build, runtime and type errors
- Inspect routes, pages and project metadata
- Find the dev server log file
- Resolve a Server Action ID to its source file
- Locate version-accurate Next.js docs in the installed package
- Get setup steps for the agent-browser CLI
Herramientas
Los servidores locales muestran sus herramientas cuando están en marcha, y este no publica su lista por adelantado. Tu cliente las muestra después de añadirlo.
Prompts de ejemplo
What errors are in my Next.js application right now?
Show me the structure of my routes in the running dev server.
What's in the Next.js development server logs?
Where are the docs for the Next.js version installed in this project?
Configuración
Todos los clientes inician Next.js DevTools en tu equipo con el mismo comando. Elige el tuyo; la página recuerda tu elección.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport stdio nextjs-devtools -- npx -y next-devtools-mcp@latest- Start Claude Code and type
/mcp. nextjs-devtools should show as connected.
Add --scope user to make it available in every project.
Claude Desktop
- Open Settings → Developer → Edit Config. It opens
claude_desktop_config.json. Add:
{
"mcpServers": {
"nextjs-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}- Save the file and restart Claude Desktop.
Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.
Cursor
Añadir a Cursor (se abre en una pestaña nueva)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"nextjs-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}Needs Node.js on your computer.
VS Code
Install in VS Code (se abre en una pestaña nueva)
Or from a terminal:
code --add-mcp '{"name":"nextjs-devtools","type":"stdio","command":"npx","args":["-y","next-devtools-mcp@latest"]}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"nextjs-devtools": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}Needs Node.js on your computer.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"nextjs-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}- Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf.
Codex
codex mcp add nextjs-devtools -- npx -y next-devtools-mcp@latestOr edit ~/.codex/config.toml directly:
[mcp_servers.nextjs-devtools]
command = "npx"
args = ["-y", "next-devtools-mcp@latest"]Needs Node.js on your computer.
Gemini CLI
gemini mcp add nextjs-devtools npx -- -y next-devtools-mcp@latestThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients that start local servers accept this shape:
{
"mcpServers": {
"nextjs-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}Zed puts servers under context_servers in its settings, with the same command, args and env fields.
Needs Node.js on your computer.
Preguntas frecuentes
Can I paste mcp.tc/i/nextjs-devtools into my MCP client?
No. Next.js DevTools runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y next-devtools-mcp@latest.
Does Next.js DevTools need an API key?
No. It doesn’t declare any keys or environment variables. It runs with your user account’s permissions, so check what its tools can reach.
Is Next.js DevTools a remote or a local server?
Local. Your client starts it as a process on your computer with npx -y next-devtools-mcp@latest, which needs Node.js.
What can Next.js DevTools do?
You can discover running Next.js dev servers and list their runtime tools, read current build, runtime and type errors y inspect routes, pages and project metadata.
Which clients can use it?
Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.
Who wrote this page?
mcp.tc’s robot read Next.js DevTools’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
Insertar
Muestra Next.js DevTools en un README o en tu web. Cada inserción enlaza a esta página, usa el comando de instalación del servidor y no instala cookies. Cómo funcionan las inserciones
Insignia para README
[](https://mcp.tc/i/nextjs-devtools)<a href="https://mcp.tc/i/nextjs-devtools"><img src="https://mcp.tc/i/nextjs-devtools/badge.svg" alt="Next.js DevTools on mcp.tc" height="20"></a>Sigue el modo claro u oscuro de quien lee. Añade ?theme=light o ?theme=dark para fijarlo, o ?style=compact para mostrar el símbolo sin la palabra.
Tarjeta para web
<script src="https://mcp.tc/w/nextjs-devtools.js" async></script>La tarjeta aparece donde esté la etiqueta. Añade data-theme="dark" o data-size="compact" a la etiqueta para cambiarla. El archivo contiene todo lo que necesita, así que no hace otras solicitudes ni instala cookies.
iframe
<iframe src="https://mcp.tc/embed/nextjs-devtools" title="Next.js DevTools on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Úsalo en páginas que no permiten scripts. Añade ?theme=light o ?theme=dark a la dirección para fijar los colores.
JSON
La ficha como datos para tus propias páginas y herramientas: nombre, descripción corta, comando de instalación, herramientas y los enlaces «Add to». Cualquier web puede leerla (CORS abierto).
https://mcp.tc/i/nextjs-devtools.jsonmcp.tc no tiene relación con Vercel. Esta página se creó a partir de los metadatos públicos de Next.js DevTools, comprobados por última vez el 3 oct 2026, y un modelo de IA escribió la descripción, así que puede contener errores. Los nombres y marcas pertenecen a sus titulares. ¿Algo no cuadra? Reportar esta ficha.