
Next.js DevTools MCP Server: Setup for Claude Code, Cursor and Other Apps
Lets your coding assistant see what your running Next.js app is doing, such as build errors, routes and logs.
This is a small connector from Vercel. It finds a Next.js dev server running on your computer and passes your assistant that server's own live data. It needs Next.js 16 or newer and a running dev server for the main tools. Two other tools point the assistant at the docs that ship with Next.js and at a browser automation tool.
Good for
- Next.js developers who want the assistant to read live build and runtime errors
- Developers who want answers that match their installed Next.js version
Works in
12 should work
Tap an app to see how to set it up and any known problems.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Client does not support this transport.
Client does not support this transport.
Install next-devtools MCP
Claude Code
- 1
Copy this prompt.
Add the next-devtools MCP server to Claude Code. Run this command: claude mcp add next-devtools -- npx -y next-devtools-mcp Then check that it loaded and tell me if I need to sign in or restart.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Node.js.
Built from the package data we hold. Not yet tested by us.
Tools
Finds your running Next.js dev servers
Scans common ports for running Next.js 16+ dev servers and lists the tools each one offers.
Try: “Which Next.js dev servers are running?”
Network ·
nextjs_indexReads live errors, routes and logs from your app
Calls one of the dev server's built-in tools, such as current errors, page routes, project info or logs. Run the index tool first to see what is available.
Try: “What errors does my Next.js app have right now?”
Network ·
nextjs_callPoints to the docs for your Next.js version
Does not download docs. It finds the docs bundled with your installed Next.js and tells the assistant where to read them.
Try: “Where are the docs for the Next.js version I use?”
Files ·
nextjs_docsSets up browser testing
Checks whether the agent-browser tool is installed and returns either how to use it or how to install it. It does not drive the browser itself.
Try: “Help me test this page in a browser.”
Runs code ·
browser_eval
Read from the source code
Permissions
low risk · 2 things to watch
Low risk
It talks to your local dev server and reads errors, routes and logs, and it does not change your files itself. Usage statistics are sent anonymously, which you can turn off.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It sends anonymous usage statistics
The README says it records which tools you call, error events and basic system info, not your code. Set NEXT_TELEMETRY_DISABLED=1 to turn it off.
It can call any tool your dev server exposes
The call tool runs whatever runtime tool your Next.js version offers on your local server. Read the list it shows first.
Security advisories
No published security advisories as of Nov 1, 2026.
Technical details
| Talks to | Your local Next.js dev server. Anonymous usage telemetry (can be turned off) |
|---|
Questions
Is the Next.js DevTools MCP official?
Yes. It is published by Vercel, the company behind Next.js.
Which Next.js versions does it work with?
The main tools need Next.js 16 or newer with a running dev server. Next.js 16 turns on its built-in MCP endpoint by default.
Does it need an API key?
No. It talks to the dev server on your own computer.
What happened to the upgrade and Cache Components tools?
Version 0.4.0 removed them. Those workflows now come as agent skills, and the docs ship inside Next.js.
Does it collect data?
It sends anonymous usage statistics, such as tool names and error events, and not your code. Set NEXT_TELEMETRY_DISABLED=1 to turn it off.
How is it different from the Vercel MCP server?
This one works on your local Next.js app while you build. The Vercel server manages your Vercel account, such as deployments and projects.
Information
updated Nov 2, 2026
- Publisher
- Vercel (official)
- Package
next-devtools-mcp- Registry
- npm
- Transport
- stdio
- Version
- 0.3.6
- License
- MIT
- Last commit
- Sep 15, 2026
- Open issues
- 10
- Listed in
- Official MCP registry
Other Vercel MCP servers
Sources
Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.
Show all 1Hide
- Next.js DevTools MCP README · github.com