Connect Next.js DevTools MCP to Cline
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
- Cline 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 Cline
Add it in your editor
In Cline, open the MCP Servers panel, choose Configure, click Configure MCP Servers and add this to the file that opens.
cline_mcp_settings.json { "mcpServers": { "next-devtools": { "command": "npx", "args": [ "-y", "next-devtools-mcp@latest" ] } } }Or add it to the Cline CLI
Saves the server to the Cline CLI's own settings. The editor extension keeps a separate list.
Terminal cline mcp add next-devtools --yes -- npx -y next-devtools-mcp@latestStep 2: Check it's connected
Terminal cline config mcpIn VS Code or JetBrains, open the MCP Servers panel in Cline and check the server is listed with its tools.
Step 3: Try a first request
Ask Cline something that only works with Next.js DevTools MCP connected:
Say to Cline 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
- In the editor, open the MCP Servers panel, choose Configure and click Configure MCP Servers to edit
cline_mcp_settings.json. - The Cline CLI keeps its own list in
~/.cline/data/settings/cline_mcp_settings.json, separate from the editor's. - Remote servers need
"type": "streamableHttp". Without it, Cline falls back to the older SSE transport.





