OfficialDev & code hostinglocal stdio

Next DevTools MCP

Q: Which Next.js version does Next DevTools MCP need?

Next.js 16 or later with a running dev server for nextjs_index and nextjs_call. The nextjs_docs and browser_eval gateways work without a dev server.

Q: Does Next DevTools MCP need an API key or configuration?

No. It runs locally through npx, and Next.js 16+ exposes its MCP endpoint at /_next/mcp by default, which the server finds on its own.

Q: Where did the upgrade and Cache Components tools go?

Version 0.4.0 removed upgrade_nextjs_16, enable_cache_components and the init tool. The README says those workflows now ship as agent skills, and docs come from the copy bundled with Next.js.

Connects agents to a running Next.js 16+ dev server for live errors, routes, logs and Server Actions.

Install

Any MCP client

(project .mcp.json or the client’s MCP settings)

{
  "mcpServers": {
    "next-devtools": {
      "command": "npx",
      "args": ["-y", "next-devtools-mcp@latest"]
    }
  }
}

All detected agents

(with add-mcp; add -y to skip the prompt, -g to install globally)

npx add-mcp next-devtools-mcp@latest

Claude Code

claude mcp add next-devtools npx next-devtools-mcp@latest

Codex

codex mcp add next-devtools -- npx next-devtools-mcp@latest

Cursor

Cursor Settings → MCP → New MCP Server, with the JSON configuration above.

Gemini CLI

# Project
gemini mcp add next-devtools npx next-devtools-mcp@latest

# Global
gemini mcp add -s user next-devtools npx next-devtools-mcp@latest

Google Antigravity

(.gemini/antigravity/mcp_config.json)

{
  "mcpServers": {
    "next-devtools": {
      "command": "npx",
      "args": ["-y", "next-devtools-mcp@latest"]
    }
  }
}

VS Code / Copilot

code --add-mcp '{"name":"next-devtools","command":"npx","args":["-y","next-devtools-mcp@latest"]}'

Commands and configuration as given in the repository README. Start your Next.js dev server (npm run dev) before asking the agent about the running app.

Next DevTools MCP is Vercel’s official server that connects coding agents to a running Next.js 16+ dev server.

Next DevTools MCP (next-devtools-mcp) is a thin connector: it discovers running Next.js 16+ dev servers and proxies their built-in MCP endpoint (/_next/mcp), so agents get live runtime errors, routes and logs. It runs locally over stdio through npx, needs no API key, and is licensed MIT (README). The Next.js documentation points to this package for coding agents on Next.js 16 and above (Next.js MCP guide). This listing reflects version 0.4.1 in the repository’s package.json.

It has four tools. nextjs_index finds running dev servers and lists their runtime tools; nextjs_call calls one of them, such as get_errors, get_logs, get_page_metadata, get_project_metadata or get_server_action_by_id. Two gateways point the agent elsewhere: nextjs_docs sends it to the version-matched docs Next.js bundles in node_modules/next/dist/docs/, and browser_eval to the agent-browser CLI. Next.js 16+ enables its MCP endpoint by default at http://localhost:3000/_next/mcp, and the server connects to it without configuration (README).

The server collects anonymous usage telemetry (tool names, error messages, session metadata; not code, file paths or tool arguments). Turn it off with export NEXT_TELEMETRY_DISABLED=1 (README, Privacy & Telemetry).

Questions

Which Next.js version does Next DevTools MCP need?

Next.js 16 or later with a running dev server for nextjs_index and nextjs_call. The nextjs_docs and browser_eval gateways work without a dev server.

Does Next DevTools MCP need an API key or configuration?

No. It runs locally through npx, and Next.js 16+ exposes its MCP endpoint at /_next/mcp by default, which the server finds on its own.

Does it collect telemetry?

Yes, anonymous usage data: which tools are called, error messages and session metadata. Set NEXT_TELEMETRY_DISABLED=1 to opt out; local data lives in ~/.next-devtools-mcp/.

Where did the upgrade and Cache Components tools go?

Version 0.4.0 removed upgrade_nextjs_16, enable_cache_components and the init tool. The README says those workflows now ship as agent skills, and docs come from the copy bundled with Next.js.

Sources

Checked October 4, 2026.

Dev & code hosting

View all