Connect Next.js DevTools MCP to Devin Desktop
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
- Devin Desktop (formerly Windsurf) 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 Devin Desktop
Add it from the terminal
Run this in your project folder. It saves the server for you in
.devin/mcp_config.local.json, which isn't committed.Terminal devin mcp add next-devtools -- npx -y next-devtools-mcp@latestOr share it with your team
Add this to
.devin/mcp_config.jsonand commit it, or to~/.config/devin/mcp_config.jsonto use it in every project..devin/mcp_config.json { "mcpServers": { "next-devtools": { "command": "npx", "args": [ "-y", "next-devtools-mcp@latest" ] } } }Step 2: Check it's connected
Terminal devin mcp listIn Devin Desktop, open Customize from the Agents window, choose MCPs and check the server under This computer.
Step 3: Try a first request
Ask Devin Desktop something that only works with Next.js DevTools MCP connected:
Say to Devin Desktop 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
- Devin Desktop and the Devin CLI share the same MCP files:
.devin/mcp_config.jsonin a project,.devin/mcp_config.local.jsonfor just you, and~/.config/devin/mcp_config.jsonfor every project. - Servers set up in Windsurf's old
mcp_config.jsonaren't read. Add them again in the Devin format. - Servers that need a sign-in: run
devin mcp login <name>, or click Authenticate next to the server.





