Next Devtools MCP: Inspect Next.js errors and routes

Understand the project

Practical overview

When it fits

Use it during Next.js development when a coding agent needs to inspect the state of a running app or be directed to version-specific documentation and a browser automation CLI.

Who it is for

Next.js developers using coding agents such as Claude or Cursor
Teams seeking agent access to live development-server diagnostics

Documented uses

Discover running Next.js development servers and their available runtime tools.
Query current build, runtime and type errors, routes, project metadata and development logs.
Resolve a Server Action ID to its source file when the running server exposes that tool.
Direct an agent to Next.js documentation bundled for the installed version or to the agent-browser CLI.

Before you choose

Requirements & limits

The project is published as a public GitHub repository and documents installation through npm tooling.

Runtime discovery and calls require Next.js 16+ and an active development server.
The runtime tools available depend on the Next.js version.
Documentation and browser automation are exposed as gateways: the agent uses the referenced documentation or CLI directly rather than having the MCP server perform those tasks.
The documented setup requires Node.js v20.19 or a newer LTS release and npm or pnpm.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Connect an MCP client to a Next.js development server

Set up Next Devtools MCP and use an agent to query runtime information from a running Next.js 16+ app.

Before you start

Node.js v20.19 or a newer LTS version
npm or pnpm
Next.js 16+ with a running development server
An MCP client configured for the server

Steps

Install Next Devtools MCP with the command below, or add the documented the command below command to the MCP client configuration.
Documented command
```
npx add-mcp next-devtools-mcp@latest
```
Documented command
```
npx -y next-devtools-mcp@latest
```
Start the Next.js development server.
Ask the coding agent to inspect errors, routes or development logs; it discovers the server with nextjs_index and queries it with nextjs_call.

Expected outcome

The agent can query runtime tools exposed by the discovered Next.js server, such as current errors, route metadata and logs.

Guide limitations

Runtime discovery and calls require Next.js 16+ with a running development server.
The set of runtime tools exposed by Next.js varies by version.

Documentation 1 ↗

COMPARE OPTIONS

Compare options for AI coding assistance

These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.

Project	Documented purpose	Platform	Access and requirements
Next Devtools MCP	Discover running Next.js development servers and their available runtime tools.	CLI, Server, Self-hosted	The project is published as a public GitHub repository and documents installation through npm tooling.
Figwright	Convert a selected Figma design into framework-aware code informed by layout, typography, variables and components.	CLI, Server	The project describes the server as free and says the free Figma tier is sufficient. A Figma desktop app is required to import the development plugin. The repository is public and MIT-licensed.
Ffmpeg Skill	Cut, join or shorten footage by removing silence.	CLI, Server, Self-hosted	The public repository is MIT-licensed. The documented setup uses local FFmpeg and Python; the npx installer requires Node.

Evidence and transparency

Sources & review

Official repository ↗

Source record details

Source availability: Active
Sources checked: 6 November 2026
Original website title: vercel/next-devtools-mcp · Official homepage title · retained in its source language

How we review sources Suggest a correction

Next Devtools MCP