Next Devtools MCP
by vercel
Connects coding agents to running Next.js 16+ dev servers for runtime errors, routes, logs, docs, and browser automation guidance.
Install Next Devtools MCP
Pick your client, then add it in one click or paste the config.
~/Library/Application Support/Claude/claude_desktop_config.json{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.
We couldn’t confirm it starts correctly
We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.
npx -y next-devtools-mcp@latestNo response to initialize.
This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 25d ago.
Overview
Use cases
- Inspect errors in a running Next.js application
- Discover routes and page metadata during development
- Review development server logs through an agent
- Find documentation matching the installed Next.js version
- Set up browser automation guidance with agent-browser
Key features
- Discovers running Next.js development servers
- Proxies runtime errors, routes, logs, and metadata
- Resolves Server Action IDs to source files
- Locates version-specific bundled Next.js docs
- Guides agents toward agent-browser CLI usage
How Next Devtools MCP works
Tools4
What Next Devtools MCP lets your agent do. Expand a tool for its parameters.
Security & health
What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.
ActiveLast checked Today
Recent health check succeeded.
15/16 checks healthy over the last 70d
Supply-chain signal
No high-severity advisories surfaced by our automated scan.
Critical 0High 0Medium 0Low 0
Scanned 13d ago via OSV.dev · next-devtools-mcp@latest (npm)
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
GitHub stars831Stargazers on the source repository.
npm downloads472kPackage downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed4Callable tools this server registers over MCP.
Directory activity1 upvotesConfig copies, upvotes, and views on AllMCPs.
Reviews
No reviews yet — be the first to share how it worked for you.
Frequently Asked Questions about Next Devtools MCP
Configure the client to run `npx -y next-devtools-mcp@latest`, or use a client-specific MCP setup command documented by the project.
Its runtime discovery and runtime calls require Next.js 16 or newer with a running development server. The docs gateway recommends an upgrade path for older versions.
Call `nextjs_index` to discover a server, then call `nextjs_call` with its port and a runtime tool such as `get_errors` or `get_page_metadata`.
Yes. The README provides a Cursor MCP configuration using `npx -y next-devtools-mcp@latest`.
Related MCP servers
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/vercel-next-devtools-mcp)HTML Embed
<a href="https://allmcps.com/mcp/vercel-next-devtools-mcp"><img src="https://allmcps.com/api/badge/vercel-next-devtools-mcp?style=directory" alt="Next Devtools MCP on AllMCPs" /></a>