Next Devtools MCP

What vercel/next-devtools-mcp MCP server does

The vercel/next-devtools-mcp MCP server connects an MCP-compatible coding agent with local Next.js development servers. Its primary role is discovery and forwarding: it finds running Next.js 16+ servers, lists the runtime tools exposed by each one, and sends requested calls to the selected server.

Runtime results can include current build, runtime, and type errors; development logs; route and page metadata; project metadata; and the source file associated with a Server Action ID. The server also exposes two gateways. One identifies the version-specific documentation bundled inside a project’s node_modules/next/dist/docs/ directory, while the other reports how to use the agent-browser command-line tool for browser automation.

How it works

Start a Next.js development process, such as with npm run dev, before requesting runtime information. Next.js 16+ exposes its MCP endpoint at /_next/mcp, and the connector scans common ports to locate available servers. No project or server URL configuration is needed for the automatic discovery flow.

Agents normally call nextjs_index first. The response includes discovered server details such as port, process ID, URL, and available runtime tools. They can then pass the selected port and a runtime tool name to nextjs_call; an optional arguments object is available when that runtime tool needs parameters.

The gateway tools do not fetch documentation or execute browser actions through MCP. nextjs_docs returns the local documentation path and reading instructions, and browser_eval detects whether agent-browser is installed or returns installation guidance. The agent then performs those tasks directly.

Setup and configuration

Install the npm package with a client configuration that runs npx -y next-devtools-mcp@latest. The project documents setup for clients including Cursor, Claude Code, Codex, Gemini, Google Antigravity, VS Code/Copilot, and Warp. Node.js 20.19 or a newer LTS release is required, along with npm or pnpm.

After adding the MCP server to the client, launch the Next.js development server. Runtime discovery and calls require a running Next.js 16+ application. The documentation gateway uses the installed Next.js package; for older Next.js versions, it recommends the latest Next.js upgrade codemod.

Tools and capabilities

• nextjs_index scans for running Next.js development servers and lists their runtime MCP tools.
• nextjs_call invokes a named runtime tool on a discovered server using its port.
• nextjs_docs locates version-accurate documentation bundled with Next.js.
• browser_eval checks for agent-browser and provides the command or installation steps needed to use it.

Limitations and notes

The vercel/next-devtools-mcp MCP server is a thin connector, so live runtime capabilities depend on a reachable Next.js 16+ development server. The gateway tools are pointers rather than document fetchers or browser drivers. Upgrade and Cache Components workflows are no longer implemented as server tools; they are distributed as agent skills.

Anonymous telemetry records tool names, anonymous error messages, session metadata, and basic environment details. It does not collect code, file contents or paths, personal data, credentials, or tool arguments. Local telemetry files are stored under ~/.next-devtools-mcp/. Set NEXT_TELEMETRY_DISABLED=1 to opt out, and remove that directory to delete local telemetry data.