Next.js DevTools MCP

Gives coding agents live errors, routes and logs from a running Next.js dev server.

Official
Local
stdio
v0.3.6

Official: the MCP registry verified that the publisher controls the GitHub account vercel, which this server's name is under. Source: MCP registry, checked 2026-09-25.

Repository

How to connect

Your client starts the npm package with npx, which needs Node.js. Some servers also need an API key or arguments; the repository's README says which.

Terminal

claude mcp add --transport stdio next-js-devtools -- npx -y next-devtools-mcp

~/.cursor/mcp.json

{
  "mcpServers": {
    "next-js-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "next-devtools-mcp"
      ]
    }
  }
}

~/.codex/config.toml

[mcp_servers.next-js-devtools]
command = "npx"
args = ["-y", "next-devtools-mcp"]

Syntax from each client's docs, checked 2026-09-25: Claude Code, Cursor, Codex.

Details

Official: Yes
Runs: Local
Transport: stdio
Installs from: npm
Registry version: 0.3.6
License: Not listed
Registry name: io.github.vercel/next-devtools-mcp
Repository: vercel/next-devtools-mcp
npm package: next-devtools-mcp

Remote, local, transport and packages are read off the registry's platforms. Source: MCP registry, checked 2026-09-25.

Maintenance

Counts as checked on the day shown. Not a rating.

13 contributors on GitHub as of 2026-09-25.

Also by Vercel10

All 11 by Vercel

Friday

The brief, by email

Five to seven links an issue, each with what to do about it.

Unsubscribe from any issue.

This page as Markdown