Verbindet Coding-Agents mit einem laufenden Next.js Dev-Server für Live-Errors, Routes, Logs und Server Actions.
Auch bekannt als vercel/next-devtools-mcp
- Stars
- 836
- Tools
- 12
- Downloads, 30 Tage
- —
- Neueste Version
- 0.3.6
- Letzter Commit
- 15. Sept. 2026
- Lizenz
- —
Was ist Next.js DevTools MCP?
Verbindet Coding-Agents mit einem laufenden Next.js Dev-Server für Live-Errors, Routes, Logs und Server Actions. Er stellt 12 Tools bereit, etwa nextjs_index, nextjs_call, nextjs_docs.
Zusammenfassung generiert aus dem README des Projekts
Über Next.js DevTools MCP server
Dieses Tool ermöglicht es Entwicklern, die Claude, Cursor oder andere MCP-kompatible Clients nutzen, Coding-Agents direkt mit einem laufenden Next.js Development-Server zu verbinden. Es fungiert als schlanker Connector, der Next.js 16+ Dev-Server automatisch erkennt, indem er nach deren eingebauten MCP-Endpoints scannt. Dadurch kann ein AI-Agent direkt mit deiner lokalen Runtime-Umgebung interagieren, um den Live-Status zu inspizieren.
Nutzer können das nextjs_index Tool verwenden, um aktive Server zu finden, und das nextjs_call Tool, um spezifische Runtime-Daten wie Build-Errors, Server-Logs, Application-Routes und Server Actions abzufragen. Der Server bietet zudem Gateways, die Agents helfen, auf versionsgenaue Dokumentationen innerhalb deiner node_modules zuzugreifen oder Browser-Automatisierung via agent-browser CLI einzurichten. Für die Funktion sind Node.js v20.19 oder neuer und ein laufender Next.js 16+ Development-Server erforderlich.
Was du damit machen kannst
- 1Live-Runtime-Errors debuggenBitte deinen AI-Agent, aktuelle Build- oder Runtime-Errors in deiner Next.js-Applikation zu identifizieren und zu erklären.
- 2Application-Routing inspizierenLass einen Agent die Struktur deiner Routes und Page-Metadaten vom aktiven Dev-Server abrufen.
- 3Versionsspezifische Dokumentation nutzenLeite einen Agent direkt zur Dokumentation, die mit deiner spezifisch installierten Next.js-Version gebündelt ist, um maximale Genauigkeit zu gewährleisten.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Next.js DevTools MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenNext.js DevTools MCP in Claude Code installieren
$ claude mcp add next-devtools-mcp -- npx -y next-devtools-mcpNext.js DevTools MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp"
]
}
}
}Next.js DevTools MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"next-devtools-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"next-devtools-mcp"
]
}
}
}Next.js DevTools MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"next-devtools-mcp","type":"stdio","command":"npx","args":["-y","next-devtools-mcp"]}'Next.js DevTools MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp"
]
}
}
}Next.js DevTools MCP in Codex installieren
$ codex mcp add next-devtools-mcp -- npx -y next-devtools-mcpNext.js DevTools MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.next-devtools-mcp] command = "npx" args = ["-y", "next-devtools-mcp"]
Next.js DevTools MCP in Gemini CLI installieren
$ gemini mcp add -s user next-devtools-mcp npx -- -y next-devtools-mcpNext.js DevTools MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp"
]
}
}
}Next.js DevTools MCP tools 12
Erkannt aus dem READMEnextjs_indexnextjs_callnextjs_docsbrowser_evalget_errorsget_logsget_page_metadataget_project_metadataget_server_action_by_idporttoolNameargs
| nextjs_index | — | |
| nextjs_call | — | |
| nextjs_docs | — | |
| browser_eval | — | |
| get_errors | — | |
| get_logs | — | |
| get_page_metadata | — | |
| get_project_metadata | — | |
| get_server_action_by_id | — | |
| port | — | |
| toolName | — | |
| args | — |
Konfiguration
NEXT_TELEMETRY_DISABLED
| Name | Beschreibung | Typ |
|---|---|---|
| NEXT_TELEMETRY_DISABLED | — |
Automatisierte Checks
Geluften am 12. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren · Was du für mehr Punkte verbessern kannst
- Source Repository verknüpft und erreichbarBestanden
- Open Source Lizenz (OSI)No licenseBefund
- Commit oder Release im letzten JahrBestanden
- Package-Name ähnelt keinem populären PackageBestanden
- Remote Endpoint nutzt HTTPSNicht geprüft
- Destruktive Tools sind markiertBestanden
- Keine versteckten Anweisungen an das ModellBestanden
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenBestanden
README
Auf GitHub ansehenNext.js DevTools MCP
next-devtools-mcp is a Model Context Protocol (MCP) server 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.
[!NOTE] 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. See Migrating from 0.3.x.
Requirements
- Node.js v20.19 or a newer LTS version
- npm or pnpm
- Next.js 16+ with a running dev server (for
nextjs_index/nextjs_call)
Install
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 across all projects.
Or add the config to your MCP client manually:
{
"mcpServers": {
"next-devtools": {
"command": "npx",
"args": ["-y", "next-devtools-mcp@latest"]
}
}
}
[!NOTE]
next-devtools-mcp@latestkeeps your client on the latest version.
Client-specific setup
amp mcp add next-devtools -- npx next-devtools-mcp@latest
Or follow Amp's MCP docs with the config above.
claude mcp add next-devtools npx next-devtools-mcp@latest
Or edit your MCP settings file with the config above.
codex mcp add next-devtools -- npx next-devtools-mcp@latest
Windows 11: add environment variables and a longer startup timeout to .codex/config.toml:
env = { SystemRoot="C:\\Windows", PROGRAMFILES="C:\\Program Files" }
startup_timeout_ms = 20_000
Or go to Cursor Settings → MCP → New MCP Server and use the config above.
# Project
gemini mcp add next-devtools npx next-devtools-mcp@latest
# Global
gemini mcp add -s user next-devtools npx next-devtools-mcp@latest
Add to .gemini/antigravity/mcp_config.json:
{
"mcpServers": {
"next-devtools": {
"command": "npx",
"args": ["-y", "next-devtools-mcp@latest"]
}
}
}
See the Antigravity MCP docs.
code --add-mcp '{"name":"next-devtools","command":"npx","args":["-y","next-devtools-mcp@latest"]}'
Or follow the official VS Code MCP setup guide.
Settings | AI | Manage MCP Servers → + Add:
- Name:
next-devtools - Command:
npx - Arguments:
-y, next-devtools-mcp@latest
Quick Start
Start your Next.js dev server:
npm run dev
Next.js 16+ enables its MCP endpoint by default at http://localhost:3000/_next/mcp. next-devtools-mcp discovers and connects to it automatically — no config needed.
Then ask your agent about the running app:
Next Devtools, what errors are in my Next.js application?
Next Devtools, show me the structure of my routes
Next Devtools, what's in the development server logs?
The agent calls nextjs_index to discover servers, then nextjs_call to query their real state.
Tools
| Tool | What it does |
|---|---|
nextjs_index |
Discover running Next.js dev servers and list each one's runtime MCP tools. |
nextjs_call |
Call a runtime tool on a discovered server (errors, routes, logs, Server Actions). |
nextjs_docs |
Gateway. Point the agent at version-accurate docs in node_modules/next/dist/docs/. |
browser_eval |
Gateway. Point the agent at the agent-browser CLI for browser automation. |
The gateways do not do the work themselves — they tell the agent where the docs are or how to install/run the CLI, and the agent runs it directly (faster than proxying through MCP).
Scans common ports for running Next.js 16+ dev servers and lists each server's built-in runtime tools at /_next/mcp. No parameters.
Runtime tools exposed by Next.js (varies by version):
get_errors— current build, runtime, and type errorsget_logs— path to the dev log file (browser console + server output)get_page_metadata— routes, pages, component metadataget_project_metadata— project structure, config, dev server URLget_server_action_by_id— resolve a Server Action ID to its source file
Output: JSON listing discovered servers (port, PID, URL) and their tools.
Calls one runtime tool on a discovered server. Run nextjs_index first to find the port and tool name.
Input:
port(required) — dev server porttoolName(required) — runtime tool to invokeargs(optional) — arguments object, only if the tool requires them
{ "port": 3000, "toolName": "get_errors" }
Output: JSON with the tool's result. Upstream requests, including response-body reads, have a 60-second deadline. Cancelling an MCP request aborts its upstream network work; discovery also releases response bodies used only to detect the protocol.
Does not fetch docs. Recent Next.js releases bundle their docs (markdown, matching your installed version) at node_modules/next/dist/docs/. This tool checks for those files before returning reading instructions. If an installed release has no bundled docs (including early 16.x releases), it offers https://nextjs.org/docs as a fallback and asks the agent to verify APIs against the installed version. Missing dependencies receive installation guidance instead. On Next.js below 16, it recommends npx @next/codemod@latest upgrade latest.
Input: topic (optional), project_path (optional, defaults to cwd). The tool resolves next/package.json from that project, including hoisted workspace dependencies, and returns an absolute docsPath for the installed package.
Does not drive the browser. It detects whether agent-browser is installed and returns either the entry point (agent-browser skills get core --full) or the install steps (npm install -g agent-browser, then agent-browser install), so the agent runs the CLI directly.
Input: task (optional) — used only to tailor the guidance.
Migrating from 0.3.x
Starting in 0.4.0, next-devtools-mcp is a thin connector.
Changed:
nextjs_docsno longer fetches docs over the network. It points the agent at the docs Next.js bundles atnode_modules/next/dist/docs/(or recommends upgrading). Thenextjs-docs://llms-indexresource is removed.
Removed:
inittool — it only enforced the old docs-fetch workflow.upgrade_nextjs_16andenable_cache_componentstools and their prompts — now distributed as agent skills.- All
cache-components://,nextjs16://, andnextjs-fundamentals://resources — superseded by the bundled docs.
What remains: nextjs_index, nextjs_call, nextjs_docs, and browser_eval.
Privacy & Telemetry
next-devtools-mcp collects anonymous usage telemetry to improve the tool:
- Tool usage — which MCP tools are invoked (e.g.
nextjs_index,nextjs_call) - Error events — anonymous error messages when tools fail
- Session metadata — session ID, timestamps, basic environment (OS, Node.js version)
Not collected: your code, file contents or paths, personal data, credentials, or tool arguments (only tool names).
Local files live under ~/.next-devtools-mcp/ (anonymous telemetry-id, telemetry-salt, and a debug log mcp.log).
Opt out by setting the environment variable (add it to ~/.zshrc / ~/.bashrc to persist):
export NEXT_TELEMETRY_DISABLED=1
Delete local telemetry data anytime:
rm -rf ~/.next-devtools-mcp
Troubleshooting
ERR_MODULE_NOT_FOUND referencing next-devtools-mcp/dist — clear your npx cache and restart your MCP client. The server reinstalls fresh.
[error] No server info found — nextjs_index / nextjs_call need a running Next.js 16+ dev server:
- Start it:
npm run dev - Confirm Next.js 16+ (the
/_next/mcpendpoint only exists there) - Verify it started without errors
browser_eval and nextjs_docs work without a dev server.
Local Development
git clone https://github.com/vercel/next-devtools-mcp.git
cd next-devtools-mcp
pnpm install
pnpm build
Point your MCP client at the local build:
{
"mcpServers": {
"next-devtools": {
"command": "node",
"args": ["/absolute/path/to/next-devtools-mcp/dist/index.js"]
}
}
}
Or with Codex:
codex mcp add next-devtools-local -- node dist/index.js
See the Next.js MCP documentation for how MCP works with Next.js and coding agents.
License
MIT
Next.js DevTools MCP Fragen
Wie füge ich Next.js DevTools MCP zu Claude Code hinzu?
Führe claude mcp add next-devtools-mcp -- npx -y next-devtools-mcp in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Next.js DevTools MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Welche Tools bietet Next.js DevTools MCP?
Er stellt 12 Tools bereit, darunter nextjs_index, nextjs_call, nextjs_docs, browser_eval, get_errors.
Was macht next-devtools-mcp?
Es erkennt laufende Next.js 16+ Dev-Server und proxied deren eingebauten MCP-Endpoint, sodass Agents Live-Runtime-Errors, Routes und Logs erhalten.
Was sind die Voraussetzungen für next-devtools-mcp?
Du benötigst Node.js v20.19 oder neuer sowie Next.js 16+ mit einem laufenden Dev-Server für die Runtime-Tools.
Wie installiere ich next-devtools-mcp?
Führe npx add-mcp next-devtools-mcp@latest aus oder füge es deiner MCP-Client-Config hinzu, indem du npx -y next-devtools-mcp@latest als Command nutzt.
Welche Tools stellt next-devtools-mcp bereit?
Es stellt nextjs_index, nextjs_call, nextjs_docs und browser_eval bereit.
Sammelt next-devtools-mcp Telemetrie?
Ja, es sammelt anonyme Telemetrie zur Tool-Nutzung und zu Fehlern, die du mit NEXT_TELEMETRY_DISABLED=1 deaktivieren kannst.