Next DevTools MCP Server

Next.js 16+ dev server telemetry and runtime diagnostics for AI coding agents.

Data last scanned yesterday · Reviewed today

404 tools★ 801TypeScript

Overview

Next DevTools MCP Server provides a bridge between AI coding agents and your active Next.js development environment. By proxying the built-in /_next/mcp endpoint, it allows agents to access live runtime logs, route information, and current errors directly from a running Next.js 16+ server. Beyond diagnostic data, the server acts as a gateway for specialized developer tools. It links AI assistants to documentation resources and the agent-browser CLI, facilitating context-aware development workflows without manual file navigation.

Our verdict

This server carries a high risk level with a security score of 40/100. The score reflects that the project is community-maintained rather than vendor-official and notably lacks a defined license, leaving its legal usage terms unclear. Due to these potential governance and liability concerns, it is best suited for experimental environments rather than sensitive or restricted infrastructure.

Supports live runtime error and log retrieval
Provides gateways for version-accurate documentation
Small footprint with only five direct dependencies
Integrates with the agent-browser CLI tool

Community-maintained with no official vendor support
No license detected for usage terms
Authentication methods not yet editorially reviewed

Setup

Claude Desktop

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

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.

No read-only mode — running this grants full read/write access.
No built-in authentication — anyone with access to this config can invoke every tool it exposes.

Tools

Tool	Description	Risk
nextjs_index	Discover running Next.js dev servers and list each one's runtime MCP tools.	low
nextjs_call	Call a runtime tool on a discovered server (errors, routes, logs, Server Actions).	low
nextjs_docs	Point the agent at version-accurate docs in node_modules/next/dist/docs/.	low
browser_eval	Point the agent at the agent-browser CLI for browser automation.	low

Compatibility

Client	Local	Docker	Remote	Read-only
Claude Desktop
Cursor
VS Code
Windsurf
ChatGPT

Frequently asked questions

›What are the specific software requirements to run this server?

You must have Node.js v20.19 or a newer LTS version installed, along with either npm or pnpm.

›Do I need to manually configure the server to connect to my Next.js application?

No, the server automatically discovers running Next.js 16+ dev servers at localhost without requiring additional configuration.

›What is the primary function of the provided gateway tools?

The gateway tools do not perform actions directly; instead, they point the agent to local documentation or the agent-browser CLI so the agent can execute those tasks directly.

›Are there any platform-specific requirements for Windows users?

Yes, if using Codex on Windows 11, you must add specific environment variables and increase the startup timeout in your .codex/config.toml file.

›What information does the nextjs_index tool provide?

This tool scans for running Next.js 16+ dev servers and returns a JSON list of discovered servers, including their ports, PIDs, URLs, and available runtime tools.