Official server by Vercel
Next.js DevTools MCP server
Gives coding agents Next.js docs, runtime errors and upgrade helpers for your app.
Install
Pick your agent and copy one line. Remote servers ask you to sign in on first use.
claude mcp add next-devtools -- npx -y next-devtools-mcp
# ~/.codex/config.toml [mcp_servers.next_devtools] command = "npx" args = ["-y", "next-devtools-mcp"]
gemini mcp add next-devtools npx -y next-devtools-mcp
{
"mcpServers": {
"next-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp"
]
}
}
}code --add-mcp '{"name":"next-devtools","command":"npx","args":["-y","next-devtools-mcp"]}'What it can do
From Vercel's own MCP documentation.
Sign in
None. It runs locally with npx next-devtools-mcp@latest.
Tools (4)
nextjs_indexnextjs_callnextjs_docsbrowser_eval
Options
- Install with npx add-mcp next-devtools-mcp@latest or claude mcp add next-devtools npx next-devtools-mcp@latest.
- nextjs_call can reach runtime tools on the dev server such as get_errors, get_logs, get_page_metadata, get_project_metadata and get_server_action_by_id. These vary by version.
- Disable telemetry with NEXT_TELEMETRY_DISABLED=1.
Good to know
- Needs Node.js v20.19 or newer.
- nextjs_index and nextjs_call need a running Next.js 16+ dev server. Otherwise they fail with No server info found.
- nextjs_index only scans common ports.
- Version 0.4.0 removed the init, upgrade_nextjs_16 and enable_cache_components tools.
- Telemetry collects tool names, anonymous error messages and session metadata, but not arguments, code or file paths.
Details
- Registry name
- io.github.vercel/next-devtools-mcp
- Latest version
- 0.3.6 (updated 2025-12-05)
- Packages
next-devtools-mcp (npm)
- Links
- Vercel docsSource
More in Developer tools
Reviewed Oct 21, 2026. Official means published under Vercel's namespace in the MCP registry. It is not a security audit.
Built an MCP server? Get it listed everywhere →
Shipping an Android app? Google Play needs 12 testers for 14 days first. Get them with Tester Exchange →