Next.js DevTools MCP

npx -y next-devtools-mcp@latest

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

Vercel describes this as a thin connector, and the description is the design: it discovers dev servers running Next.js 16 or newer and proxies the endpoint those servers already expose at /_next/mcp. The agent therefore reads the running process — the actual error that just occurred, the route table as resolved, the server logs — instead of reasoning about a static description of the project. Documentation deliberately left the server: Next.js ships its own docs inside node_modules, so answers stay pinned to the installed version, and upgrade workflows moved out into agent skills. Two tools do the work, nextjs_index to discover what is available and nextjs_call to invoke it.