MCP server · Code and developer tools
Next.js DevTools MCP server
Connects a coding assistant to your running Next.js 16 dev server so it can read live errors, routes and logs.
- Maintainer
- Vercel (official)
- Licence
- MIT
- Runs
- Locally (npx)
- Sign-in
- None
- Registry version
- 0.3.6 (updated 2025-12-05)
- Last activity
- 2026-09-15
Overview
What it does
Next.js DevTools MCP is a small connector from Vercel. It finds Next.js 16 or newer dev servers running on common local ports and passes calls through to the MCP endpoint that Next.js builds in at /_next/mcp. That gives the assistant the real state of your app: current build, runtime and type errors, the dev log, routes and page metadata, project configuration and the source file behind a Server Action ID.
Pick it when you build with Next.js and want the assistant to debug from live errors rather than guesses. Since version 0.4.0 it no longer fetches documentation. Its nextjs_docs tool points the assistant at the version-matched docs that Next.js ships in node_modules/next/dist/docs/, and browser_eval explains how to install and run the agent-browser CLI. Upgrade and Cache Components workflows have moved to agent skills. It runs with npx, and the add-mcp tool can install it for several agents at once.
Tools
What the assistant can do
- Discover running Next.js dev servers and their runtime tools (nextjs_index)
- Call runtime tools for errors, logs, page and project metadata (nextjs_call)
- Resolve a Server Action ID to its source file
- Point the assistant to version-matched bundled docs (nextjs_docs)
- Set up the agent-browser CLI for browser checks (browser_eval)
Install
Install Next.js DevTools MCP server in your app
You need:
- Node.js 20.19 or a newer LTS release
- A Next.js 16 or newer project with the dev server running
Run in your project. --scope local keeps the servers private to you in this project; use user for every project.
claude mcp add --scope local next-devtools -- npx -y next-devtools-mcp@latest
claude mcp add --scope local next-devtools -- cmd /c npx -y 'next-devtools-mcp@latest'
Project root. Commit it to share the servers with your team; each person sets the variables in their own shell.
{
"mcpServers": {
"next-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
- On native Windows (not WSL), the reference servers’ READMEs start npx through `cmd /c`: if a server won’t start, use "command": "cmd" with "args": ["/c", "npx", …].
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json (Settings → Developer → Edit Config). Restart Claude after saving.
{
"mcpServers": {
"next-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
In your project, or ~/.cursor/mcp.json for every project.
{
"mcpServers": {
"next-devtools": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
In your workspace. VS Code asks for each secret the first time a server starts and stores it securely.
{
"servers": {
"next-devtools": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
macOS/Linux: ~/.config/devin/mcp_config.json · Windows: %APPDATA%\devin\mcp_config.json. Read by the default Devin Local agent and by the legacy Cascade agent.
{
"mcpServers": {
"next-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
Want it alongside other servers? Open Next.js DevTools MCP in the MCP config generator and add the rest; it writes one file per app. The snippets follow the setup in the server’s README, checked on 2026-10-14.
Before you install
- It only talks to Next.js dev servers it finds by scanning local ports, and passes their errors, logs and route data to the assistant.
- It sends anonymous usage telemetry (tool names, error messages, session metadata). Set NEXT_TELEMETRY_DISABLED=1 to opt out.
- browser_eval may tell the assistant to install agent-browser globally with npm. Review that step before allowing it.
- A local MCP server runs with your user account’s permissions. Install it only from the source linked above. See how to choose a safe server.
Why it’s listed
Why we list it
Gives assistants first-hand runtime data from the framework itself, maintained by the company behind Next.js.
Related
More MCP servers
- GitHub MCP ServerLets an assistant read code, manage issues and pull requests, and check Actions runs in the GitHub repositories you can access.
- GitLab MCP serverGives an assistant access to GitLab projects, issues, merge requests, pipelines and search through an MCP endpoint built into GitLab.
- Sentry MCPLets a coding assistant search Sentry errors, traces and logs, triage issues and read Sentry docs while you debug.
- Figma MCP serverGives a coding assistant design context from Figma files, such as layout, variables and components, and can write back to the canvas.
- Semgrep MCP serverLets an assistant scan code for security issues with Semgrep, write custom rules and pull findings from Semgrep AppSec Platform.
- SonarQube MCP ServerConnects an assistant to SonarQube Cloud or Server to analyse code, review issues and hotspots, and check quality gates.
All MCP serversMCP config generatorGuide: MCP servers in Claude CodeGuide: what is MCP?