Next Devtools MCP server
io.github.vercel/next-devtools-mcp·v0.3.6·822 starsNext.js development tools MCP server with stdio transport
822 stars
Reviews
Write oneNobody has reviewed Next Devtools yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Next Devtools tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
nextjs_callCall a specific MCP tool on a running Next.js development server. REQUIREMENTS: - Port number of the target Next.js dev server - Tool name to execute - Optional arguments object (if the tool requires parameters) Use 'nextjs_index' first to discover available servers, tools, and their input schemas. If 'nextjs_index' auto-discovery fails, ask the user for the port and call 'nextjs_index' again with
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
- Code scan85 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 17 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
How Next Devtools compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 94/100
- higher than 96% of 48,243 servers
- Tools
- 1
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 822
- more than 95% of 28,706 servers
What its tools let an agent do: 1 read
Install Next Devtools in Claude Code, Cursor or VS Code
Runs npx -y next-devtools-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add next-devtools-mcp -- npx -y next-devtools-mcp
What the publisher says
From the Next Devtools repository's README, as published. We do not edit it. Read it on GitHub
Next.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 nextjsindex / nextjscall)
Install
Install for all your coding agents with add-mcp:
npx add-mcp next-devtools-mcp@latestAdd -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@latest keeps your client on the latest version.
Client-specific setup
Amp
amp mcp add next-devtools -- npx next-devtools-mcp@latestOr follow Amp's MCP docs with the config above.
Claude Code
claude mcp add next-devtools npx next-devtools-mcp@latestOr edit your MCP settings file with the config above.
Codex
codex mcp add next-devtools -- npx next-devtools-mcp@latestWindows 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_000Cursor
Install in Cursor
Or go to Cursor Settings → MCP → New MCP Server and use the config above.
Gemini
# Project
gemini mcp add next-devtools npx next-devtools-mcp@latest
# Global
gemini mcp add -s user next-devtools npx next-devtools-mcp@latestGoogle Antigravity
Add to .gemini/antigravity/mcp_config.json:
{
"mcpServers": {
"next-devtools": {
"command": "npx",
"args": ["-y", "next-devtools-mcp@latest"]
}
}
}See the Antigravity MCP docs.
VS Code / Copilot
code --add-mcp '{"name":"next-devtools","command":"npx","args":["-y","next-devtools-mcp@latest"]}'Or follow the official VS Code MCP setup guide.
Warp
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 devNext.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:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Next Devtools: common questions
- Is Next Devtools MCP server safe?
- Yes, by our scan: it is graded A (94/100). Read the Next Devtools safety report
- How do I install Next Devtools?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Next Devtools need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Next Devtools maintained?
- The last commit was 52 days ago (2026-09-15). The latest release is v0.3.6.
- How does Next Devtools compare with other MCP servers?
- safety score 94/100 (higher than 96% of 48,243 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.