Connect Next.js DevTools MCP to Claude Code
Vercel's MCP server for Next.js. It connects to your running dev server so agents can read build and runtime errors, routes and logs, and search the Next.js docs.
MCP serverOfficialChecked 2026-11-16
Before you start
- Claude Code installed (see its MCP documentation (opens in a new tab)).
- Next.js DevTools MCP is available on macOS, Windows and Linux.
- Needs Next.js 16 or later. Start the dev server (
npm run dev) before the agent connects; it serves the endpoint the MCP server talks to. Error and page tools read from pages open in a browser.
Step 1: Add Next.js DevTools MCP to Claude Code
Add it from the terminal
Run this in your project folder. It saves the server for you, in this project only.
Terminal claude mcp add next-devtools -- npx -y next-devtools-mcp@latestOr share it with your team
Add this to
.mcp.jsonat the project root and commit it. Teammates approve it the first time Claude Code starts..mcp.json { "mcpServers": { "next-devtools": { "type": "stdio", "command": "npx", "args": [ "-y", "next-devtools-mcp@latest" ] } } }Step 2: Check it's connected
Terminal claude mcp listStart a session and run
/mcpto see the server, its status and its tools.Step 3: Try a first request
Ask Claude Code something that only works with Next.js DevTools MCP connected:
Say to Claude Code Check my running Next.js dev server for build or runtime errors and explain how to fix the first one.
If it doesn't work
- Servers in a project
.mcp.jsonstay inactive until you approve them the first time Claude Code starts in that folder. claude mcp addsaves to the local scope by default: only you, only this project. Add--scope userto use it in every project.- If a server shows as failed, run
claude --debugto see its startup output.





