M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
N

Next.js DevTools MCP

Official
Connects coding agents to your running Next.js dev server
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #74 of 438
Stars
★ 830 Very popular
Transport
stdio (local process)
Runtime
Node.js 20.19+
Credentials
No credential needed
Last commit
Tools
4
63FMRS · C

This is the Vercel-maintained Next.js DevTools MCP server (MIT licensed, version 0.4.0). As a thin connector, it discovers Next.js 16+ dev servers and proxies their built-in /_next/mcp endpoint so coding agents get live errors, routes, and logs, while gateway tools point agents at version-accurate docs and the agent-browser CLI. It suits developers on Next.js 16+ working with MCP coding agents; it is not for non-Next.js projects or versions below 16, nor for users expecting it to fetch docs or drive the browser itself. Note the default anonymous telemetry and the 60-second upstream request deadline.

Strongest · Setup experience 15/20 Weakest · Reliability 10/20

Reliability
10/20
Security and permissions
12/20
Maintenance
12/20
Documentation
14/20
Setup experience
15/20
Why each score
Reliability 10/20
The server declares itself a thin stdio connector whose four tools (nextjs_index, nextjs_call, nextjs_docs, browser_eval) are described consistently with their behavior, and the README supplies troubleshooting (ERR_MODULE_NOT_FOUND, 'No server info found') plus a 60-second upstream deadline and abort semantics, so the happy path is plausible. However, static review sees only the README and server.json: no committed tests, no CI workflow, so the handshake, tool-list response, and timeout/abort paths cannot be verified as reproducible. It hard-depends on a running Next.js 16+ dev server, and edge cases (port discovery failure, upstream protocol detection failure) have no reviewable evidence. Per the calibration rule, no execution evidence caps this at 12; thin test/error-handling evidence lowers it to 10.
Security and permissions 12/20
No red line is evident: no credential collection, an empty environmentVariables list, local stdio transport, no exposed network port. The docs disclose telemetry scope (tool names, anonymous errors, basic environment) and state that code, file paths, personal data, credentials, and tool arguments are not collected, with an opt-out (NEXT_TELEMETRY_DISABLED=1) and a local-data deletion command. Deductions: telemetry is enabled by default (opt-out rather than confirmation), which conflicts with least-privilege expectations; nextjs_call and browser_eval reach an upstream dev server and browser-automation CLI with undisclosed side effects and no confirmation prompt for potentially consequential operations; browser_eval recommends a global npm install and execution of a third-party CLI; and the manifest's 'License: unknown' contradicts the README's MIT claim, leaving permission/ownership boundaries unclear. Main risks are visible but scoping and confirmation are incomplete, so 12.
Maintenance 12/20
The repository is not archived and shows ~819 stars with 10 open issues; version 0.4.0 with a documented 0.3.x->0.4.0 migration (removal of init, upgrade_nextjs_16, and several resources) indicates active maintenance and some version discipline. Static evidence is thin: no visible commit cadence, release frequency, dependency-update record, issue-response latency, SECURITY.md, or governance statement. The manifest lists License as unknown while the README says MIT, an inconsistency in ownership/licensing evidence. Given 'active but governance/versioning gaps', 12.
Documentation 14/20
Documentation is solid: installation via add-mcp and manual JSON config, with per-client examples for Amp, Claude Code, Codex (including Windows 11 env vars and startup timeout), Cursor, Gemini, Antigravity, VS Code/Copilot, and Warp; each of the four tools has parameters and output described, with explicit notes that nextjs_docs and browser_eval are gateways that do not do the work themselves; prerequisites (Node v20.19+, Next.js 16+), the 60-second upstream deadline and cancellation behavior, telemetry scope and opt-out, local development, and troubleshooting are all disclosed. Deductions: no explicit LICENSE file/field substantiating MIT; limited tool output examples; the port-scan range and upstream protocol detection details are not specified; telemetry retention period and destination are unspecified. This is 'usable but with hidden assumptions', so 14.
Setup experience 15/20
Setup ease is high: one-command install via npx add-mcp next-devtools-mcp@latest plus a standard mcpServers JSON block, with concrete commands for eight mainstream clients, a clone + pnpm build development path, and a Codex local example. Dependencies are only Node LTS with no API keys or OAuth, and the server is usable immediately (nextjs_index/nextjs_call require a Next.js 16+ dev server, which is documented). Deductions: @latest floats the version, so reproducibility depends on client caching and the documented ERR_MODULE_NOT_FOUND npx-cache failure requires extra troubleshooting; Windows Codex needs manual env vars and timeout; no pinned-version recommendation is given; no fallback verification path when Next.js is absent. Per calibration, without CI/tests in the static files, setup is capped at 15, hence 15.

Static review · not runListed 2026-09-10

Read the FMRS scoring method →

Fit and risk

What it can accessRuns commands or codeUses the networkControls a browser

Best for

  • Front-end developers on Next.js 16+ who want coding agents to read live dev server state directly
  • Teams using MCP-capable agent workflows such as Claude Code, Cursor, or Codex
  • Next.js projects that need version-accurate docs instead of fetching docs over the network

Not for

  • Projects not using Next.js or below version 16 (nextjs_index / nextjs_call need a running Next.js 16+ dev server)
  • Users expecting the server to fetch docs itself or drive the browser directly (nextjs_docs and browser_eval are gateways only)
  • Deployments needing non-stdio transports such as remote HTTP

Required permissions

  • Read the project's next/package.json locally to resolve the installed Next.js version and docs path
  • Network access to local dev server ports (e.g. localhost:3000) to discover and call the /_next/mcp endpoint
  • Write local files under ~/.next-devtools-mcp/ (telemetry-id, telemetry-salt, and debug log mcp.log)
  • browser_eval may prompt installation of a global CLI: npm install -g agent-browser

Risks and side effects

  • Anonymous usage telemetry is collected by default (tool usage, anonymous error messages, session ID, timestamps, and basic environment such as OS and Node.js version); your code, file contents or paths, personal data, credentials, and tool arguments are not collected. Opt out with export NEXT_TELEMETRY_DISABLED=1, and delete local telemetry data with rm -rf ~/.next-devtools-mcp.
  • Upstream requests for runtime tool calls, including response-body reads, have a 60-second deadline.
  • nextjs_docs falls back to https://nextjs.org/docs when an installed release has no bundled docs and asks the agent to verify APIs against the installed version.
  • Using next-devtools-mcp@latest keeps clients on the latest version, which may introduce unexpected changes.

Setup

Before you start

Runtime：Node.js 20.19+

Other optional settings (1)
NEXT_TELEMETRY_DISABLED optional Set to 1 to opt out of anonymous usage telemetry; not required and not a secret. Add to ~/.zshrc or ~/.bashrc to persist.
  1. Verify requirements: Node.js v20.19 or a newer LTS version, and npm or pnpm.
  2. Install for all your coding agents with add-mcp: npx add-mcp next-devtools-mcp@latest (add -y to skip the prompt and install to all detected agents, add -g to install globally).
  3. Or add the config to your MCP client manually: {"mcpServers":{"next-devtools":{"command":"npx","args":["-y","next-devtools-mcp@latest"]}}}.
  4. Client-specific commands are also available, e.g. Claude Code: claude mcp add next-devtools npx next-devtools-mcp@latest; Cursor offers an install link or Settings → MCP → New MCP Server.
  5. Start your Next.js dev server: npm run dev. Next.js 16+ enables its MCP endpoint by default at http://localhost:3000/_next/mcp, and the server discovers and connects to it automatically with no extra config.
.mcp.json 
{"mcpServers":{"next-devtools":{"command":"npx","args":["-y","next-devtools-mcp@latest"]}}}

Shown for Claude Code. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "next-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "next-devtools-mcp@latest"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

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

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

Check that nextjs_index, nextjs_call, nextjs_docs, and browser_eval appear in your client's tool list. Start a Next.js 16+ dev server with npm run dev, then ask the agent to call nextjs_index — returning discovered servers with ports and URLs confirms the connection.

Troubleshooting

  1. ERR_MODULE_NOT_FOUND referencing next-devtools-mcp/dist: clear your npx cache and restart your MCP client; the server reinstalls fresh.
  2. [error] No server info found: nextjs_index / nextjs_call need a running Next.js 16+ dev server — start it with npm run dev, confirm Next.js 16+ (the /_next/mcp endpoint only exists there), and verify it started without errors.
  3. browser_eval and nextjs_docs work without a dev server.
  4. On Windows 11 with Codex, add environment variables (SystemRoot, PROGRAMFILES) and a longer startup timeout (startup_timeout_ms = 20_000) to .codex/config.toml.
  5. For local development, run pnpm install and pnpm build first, then point your MCP client at the local build at dist/index.js.

Things to try

Once connected, you can ask your AI assistant things like:

  • Next Devtools, what errors are in my Next.js application?
  • Show me the structure of my routes
  • What's in the development server logs?
  • Find the version-accurate docs for Server Actions in my installed Next.js

Tools 4

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

Use cases

Ask your agent about errors in the running Next.js application (nextjs_index + nextjs_call with get_errors)
Inspect routes and page structure (get_page_metadata)
Read development server logs (get_logs)
Resolve a Server Action ID to its source file (get_server_action_by_id)
Get the path to version-accurate Next.js docs for the installed version (nextjs_docs)
Set up agent-browser for browser automation (browser_eval)

Supported clients

Claude Code
Cursor
Codex
Amp
Gemini
Antigravity
VS Code
Warp

Listed from the project's documentation, not tested by this site.

Overview

next-devtools-mcp is a Model Context Protocol (MCP) server maintained by Vercel that connects coding agents like Claude and Cursor to your running Next.js dev server. It 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 also ships two gateways that point agents at tools they run directly: version-accurate docs and the agent-browser CLI. As of 0.4.0, docs and migration workflows no longer live in this server; Next.js bundles its own docs at node_modules/next/dist/docs/, and upgrade / Cache Components workflows are distributed as agent skills.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 63.3k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision 1e8dcfa47897 Data synced 2026-10-19 Read the FMRS scoring method