Next.js DevTools, verified
MCP server by Vercel · Verified
Query a running Next.js dev server for runtime errors, routes and logs, and find version-matched docs from your coding agent.
Install Next.js DevTools
Runs on your machine. Your client starts it with this command:
Needs Node.js on your computer. The setup steps below show where the command goes in each client.
Share this server
Opens this page, with the install command and setup steps.
mcp.tc/i/nextjs-devtoolsAbout
Connects coding agents such as Claude Code and Cursor to a running Next.js 16+ dev server. It discovers local dev servers, proxies their built-in MCP endpoint (/_next/mcp) and returns live build and runtime errors, routes, page metadata, project config and dev logs. Two gateway tools point the agent at the docs bundled in node_modules/next/dist/docs and at the agent-browser CLI for browser automation.
Runs locally over stdio with npx -y next-devtools-mcp@latest. Requires Node.js 20.19 or newer and, for the runtime tools, a Next.js 16+ dev server started with npm run dev. No sign-in or API key is needed.
What you can do
- Discover running Next.js dev servers and list their runtime tools
- Read current build, runtime and type errors
- Inspect routes, pages and project metadata
- Find the dev server log file
- Resolve a Server Action ID to its source file
- Locate version-accurate Next.js docs in the installed package
- Get setup steps for the agent-browser CLI
Tools
Local servers list their tools once they’re running, and this one doesn’t publish its list in advance. Your client shows them after you add it.
Example prompts
What errors are in my Next.js application right now?
Show me the structure of my routes in the running dev server.
What's in the Next.js development server logs?
Where are the docs for the Next.js version installed in this project?
Set up
Every client starts Next.js DevTools on your machine with the same command. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport stdio nextjs-devtools -- npx -y next-devtools-mcp@latest- Start Claude Code and type
/mcp. nextjs-devtools should show as connected.
Add --scope user to make it available in every project.
Claude Desktop
- Open Settings → Developer → Edit Config. It opens
claude_desktop_config.json. Add:
{
"mcpServers": {
"nextjs-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}- Save the file and restart Claude Desktop.
Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"nextjs-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}Needs Node.js on your computer.
VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"nextjs-devtools","type":"stdio","command":"npx","args":["-y","next-devtools-mcp@latest"]}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"nextjs-devtools": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}Needs Node.js on your computer.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"nextjs-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}- Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf.
Codex
codex mcp add nextjs-devtools -- npx -y next-devtools-mcp@latestOr edit ~/.codex/config.toml directly:
[mcp_servers.nextjs-devtools]
command = "npx"
args = ["-y", "next-devtools-mcp@latest"]Needs Node.js on your computer.
Gemini CLI
gemini mcp add nextjs-devtools npx -- -y next-devtools-mcp@latestThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients that start local servers accept this shape:
{
"mcpServers": {
"nextjs-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}Zed puts servers under context_servers in its settings, with the same command, args and env fields.
Needs Node.js on your computer.
Embed
Show Next.js DevTools in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/nextjs-devtools)<a href="https://mcp.tc/i/nextjs-devtools"><img src="https://mcp.tc/i/nextjs-devtools/badge.svg" alt="Next.js DevTools on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/nextjs-devtools.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/nextjs-devtools" title="Next.js DevTools on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/nextjs-devtools.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Next.js DevTools card to your site.
Add the mcp.tc card for Next.js DevTools, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/nextjs-devtools.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="nextjs-devtools"><a href="https://mcp.tc/i/nextjs-devtools">Next.js DevTools on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/nextjs-devtools)
```
Reference: https://mcp.tc/embedChange history
This server runs on your computer, so we follow its npm package: each new version shows up here, with edits by its owner.
FAQ
Can I paste mcp.tc/i/nextjs-devtools into my MCP client?
No. Next.js DevTools runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y next-devtools-mcp@latest.
Does Next.js DevTools need an API key?
No. It doesn’t declare any keys or environment variables. It runs with your user account’s permissions, so check what its tools can reach.
Is Next.js DevTools a remote or a local server?
Local. Your client starts it as a process on your computer with npx -y next-devtools-mcp@latest, which needs Node.js.
What can Next.js DevTools do?
You can discover running Next.js dev servers and list their runtime tools, read current build, runtime and type errors and inspect routes, pages and project metadata.
Which clients can use it?
Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.
Does mcp.tc track changes to Next.js DevTools?
Partly. It runs on your computer, so we follow its npm package: its History tab shows each new version and edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read Next.js DevTools’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with Vercel. This page was built from Next.js DevTools’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.