Next.js development tools MCP server with stdio transport
Next.js development tools MCP server with stdio transport. That is what the next devtools mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
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.
The server publishes 9 tools. What each one is for:
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 filenextjs_index — Discover running Next.js dev servers and list each one's runtime MCP toolsnextjs_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 automationConfiguration is passed through the environment: NEXT_TELEMETRY_DISABLED. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
nextjs_index / nextjs_call)The server ships on npm as add-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Next Devtools MCP's toolset — get_errors, get_logs, get_page_metadata and 6 more — is a fair guide to whether it matches your workflow. It is maintained by vercel; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Next Devtools MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| get_errors | current build, runtime, and type errors |
| get_logs | path to the dev log file (browser console + server output) |
| get_page_metadata | routes, pages, component metadata |
| get_project_metadata | project structure, config, dev server URL |
| get_server_action_by_id | resolve a Server Action ID to its source file |
| 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](https://github.com/vercel-labs/agent-browser) CLI for browser automation. |
{
"mcpServers": {
"next-devtools": {
"command": "npx",
"args": ["-y", "add-mcp"],
"env": {
"NEXT_TELEMETRY_DISABLED": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| NEXT_TELEMETRY_DISABLED | Configuration value read at startup. | Optional |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.