next-devtools-mcp
Next.js Development for Coding Agent
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/vercel--next-devtools-mcp)HTML
<a href="/listings/vercel--next-devtools-mcp"><img src="/api/listings/vercel--next-devtools-mcp/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Install for all your coding agents with [`add-mcp`](https://www.npmjs.com/package/add-mcp):
npx add-mcp next-devtools-mcp@latest
Add `-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
<details> <summary>Amp</summary>
amp mcp add next-devtools -- npx next-devtools-mcp@latest
Or follow [Amp's MCP docs](https://ampcode.com/manual#mcp) with the config above.
</details>
<details> <summary>Claude Code</summary>
claude mcp add next-devtools npx next-devtools-mcp@latest
Or edit your MCP settings file with the config above.
</details>
<details> <summary>Codex</summary>
codex mcp add next-devtools -- npx next-devtools-mcp@latest
**Windows 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_000</details>
<details> <summary>Cursor</summary>
[Install in Cursor](https://cursor.com/en/install-mcp?name=next-devtools&config=eyJjb21tYW5kIjoibnB4IC15IG5leHQtZGV2dG9vbHMtbWNwQGxhdGVzdCJ9)
Or go to `Cursor Settings` → `MCP` → `New MCP Server` and use the config above.
</details>
<details> <summary>Gemini</summary>
# Project gemini mcp add next-devtools npx next-devtools-mcp@latest # Global gemini mcp add -s user next-devtools npx next-devtools-mcp@latest
</details>
<details> <summary>Google Antigravity</summary>
Add to `.gemini/antigravity/mcp_config.json`:
{
"mcpServers": {
"next-devtools": {
"command": "npx",
"args": ["-y", "next-devtools-mcp@latest"]
}
}
}See the [Antigravity MCP docs](https://antigravity.google/docs/mcp).
</details>
<details> <summary>VS Code / Copilot</summary>
code --add-mcp '{"name":"next-devtools","command":"npx","args":["-y","next-devtools-mcp@latest"]}'Or follow the official VS Code MCP setup guide.
</details>
<details> <summary>Warp</summary>
`Settings | AI | Manage MCP Servers` → `+ Add`: - Name: `next-devtools` - Command: `npx` - Arguments: `-y, next-devtools-mcp@latest`
</details>
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 311 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- # Next.js DevTools MCP
- [](https://npmjs.org/package/next-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`](https://github.com/vercel-labs/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](#migrating-from-03x).
- ## Requirements
- - [Node.js](https://nodejs.org/) v20.19 or a newer [LTS](https://github.com/nodejs/Release#release-schedule) version
- - [npm](https://www.npmjs.com/) or [pnpm](https://pnpm.io/)
- - Next.js 16+ with a running dev server (for `nextjs_index` / `nextjs_call`)
- ## Install
- Install for all your coding agents with [`add-mcp`](https://www.npmjs.com/package/add-mcp):
- ```bash
- npx add-mcp next-devtools-mcp@latest
- ```
- Add `-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:
- ```json
- {
- "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
- <details>
- <summary>Amp</summary>
- ```bash
- amp mcp add next-devtools -- npx next-devtools-mcp@latest
- ```
- Or follow [Amp's MCP docs](https://ampcode.com/manual#mcp) with the config above.
- </details>
- <details>
- <summary>Claude Code</summary>
- ```bash
- claude mcp add next-devtools npx next-devtools-mcp@latest
- ```
- Or edit your MCP settings file with the config above.
- </details>
- <details>
- <summary>Codex</summary>
- ```bash
- codex mcp add next-devtools -- npx next-devtools-mcp@latest
- ```
- **Windows 11:** add environment variables and a longer startup timeout to `.codex/config.toml`:
- ```toml
- env = { SystemRoot="C:\\Windows", PROGRAMFILES="C:\\Program Files" }
- startup_timeout_ms = 20_000
- ```
- </details>
- <details>
- <summary>Cursor</summary>
- [Install in Cursor](https://cursor.com/en/install-mcp?name=next-devtools&config=eyJjb21tYW5kIjoibnB4IC15IG5leHQtZGV2dG9vbHMtbWNwQGxhdGVzdCJ9)
- Or go to `Cursor Settings` → `MCP` → `New MCP Server` and use the config above.
- </details>
- <details>
- <summary>Gemini</summary>
- ```bash
- # Project
- gemini mcp add next-devtools npx next-devtools-mcp@latest
- # Global
- gemini mcp add -s user next-devtools npx next-devtools-mcp@latest
- ```
- </details>
- <details>
- <summary>Google Antigravity</summary>
- Add to `.gemini/antigravity/mcp_config.json`:
- ```json
- {
- "mcpServers": {
- "next-devtools": {
- "command": "npx",
- "args": ["-y", "next-devtools-mcp@latest"]
- }
- }
- }
- ```
- See the [Antigravity MCP docs](https://antigravity.google/docs/mcp).
- </details>
- <details>
- <summary>VS Code / Copilot</summary>
- ```bash
- code --add-mcp '{"name":"next-devtools","command":"npx","args":["-y","next-devtools-mcp@latest"]}'
- ```
- Or follow the official VS Code MCP setup guide.
- </details>
- <details>
- <summary>Warp</summary>
- `Settings | AI | Manage MCP Servers` → `+ Add`:
- - Name: `next-devtools`
- - Command: `npx`
- - Arguments: `-y, next-devtools-mcp@latest`
- </details>
- ## Quick Start
- Start your Next.js dev server:
- ```bash
- npm run dev
- ```
- Next.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:
- ```
- Next Devtools, what errors are in my Next.js application?
- Next Devtools, show me the structure of my routes
- Next Devtools, what's in the development server logs?
- ```
- The agent calls `nextjs_index` to discover servers, then `nextjs_call` to query their real state.
- ## Tools
- | Tool | What it does |
- | -------------- | ----------------------------------------------------------------------------------------- |
- | `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. |
- The gateways do not do the work themselves — they tell the agent where the docs are or how to install/run the CLI, and the agent runs it directly (faster than proxying through MCP).
- <details>
- <summary><code>nextjs_index</code> — discover servers</summary>
- Scans common ports for running Next.js 16+ dev servers and lists each server's built-in runtime tools at `/_next/mcp`. No parameters.
- Runtime tools exposed by Next.js (varies by version):
- - `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
- Output: JSON listing discovered servers (port, PID, URL) and their tools.
- </details>
- <details>
- <summary><code>nextjs_call</code> — run a runtime tool</summary>
- Calls one runtime tool on a discovered server. Run `nextjs_index` first to find the port and tool name.
- Input:
- - `port` (required) — dev server port
- - `toolName` (required) — runtime tool to invoke
- - `args` (optional) — arguments object, only if the tool requires them
- ```jsonc
- { "port": 3000, "toolName": "get_errors" }
- ```
- Output: JSON with the tool's result. Upstream requests, including response-body reads, have a 60-second deadline. Cancelling an MCP request aborts its upstream network work; discovery also releases response bodies used only to detect the protocol.
- </details>
- <details>
- <summary><code>nextjs_docs</code> — find version-accurate docs</summary>
- Does **not** fetch docs. Recent Next.js releases bundle their docs (markdown, matching your installed version) at `node_modules/next/dist/docs/`. This tool checks for those files before returning reading instructions. If an installed release has no bundled docs (including early 16.x releases), it offers https://nextjs.org/docs as a fallback and asks the agent to verify APIs against the installed version. Missing dependencies receive installation guidance instead. On Next.js below 16, it recommends `npx @next/codemod@latest upgrade latest`.
- Input: `topic` (optional), `project_path` (optional, defaults to cwd). The tool resolves `next/package.json` from that project, including hoisted workspace dependencies, and returns an absolute `docsPath` for the installed package.
- </details>
- <details>
- <summary><code>browser_eval</code> — set up browser automation</summary>
- Does **not** drive the browser. It detects whether [`agent-browser`](https://github.com/vercel-labs/agent-browser) is installed and returns either the entry point (`agent-browser skills get core --full`) or the install steps (`npm install -g agent-browser`, then `agent-browser install`), so the agent runs the CLI directly.
- Input: `task` (optional) — used only to tailor the guidance.
- </details>
- ## Migrating from 0.3.x
- Starting in 0.4.0, `next-devtools-mcp` is a thin connector.
- **Changed:**
- - `nextjs_docs` no longer fetches docs over the network. It points the agent at the docs Next.js bundles at `node_modules/next/dist/docs/` (or recommends upgrading). The `nextjs-docs://llms-index` resource is removed.
- **Removed:**
- - `init` tool — it only enforced the old docs-fetch workflow.
- - `upgrade_nextjs_16` and `enable_cache_components` tools and their prompts — now distributed as agent skills.
- - All `cache-components://`, `nextjs16://`, and `nextjs-fundamentals://` resources — superseded by the bundled docs.
- What remains: `nextjs_index`, `nextjs_call`, `nextjs_docs`, and `browser_eval`.
- ## Privacy & Telemetry
- `next-devtools-mcp` collects anonymous usage telemetry to improve the tool:
- - **Tool usage** — which MCP tools are invoked (e.g. `nextjs_index`, `nextjs_call`)
- - **Error events** — anonymous error messages when tools fail
- - **Session metadata** — session ID, timestamps, basic environment (OS, Node.js version)
- **Not collected:** your code, file contents or paths, personal data, credentials, or tool arguments (only tool names).
- Local files live under `~/.next-devtools-mcp/` (anonymous `telemetry-id`, `telemetry-salt`, and a debug log `mcp.log`).
- **Opt out** by setting the environment variable (add it to `~/.zshrc` / `~/.bashrc` to persist):
- ```bash
- export NEXT_TELEMETRY_DISABLED=1
- ```
- Delete local telemetry data anytime:
- ```bash
- rm -rf ~/.next-devtools-mcp
- ```
- ## Troubleshooting
- **`ERR_MODULE_NOT_FOUND` referencing `next-devtools-mcp/dist`** — clear your npx cache and restart your MCP client. The server reinstalls fresh.
- **`[error] No server info found`** — `nextjs_index` / `nextjs_call` need a running Next.js 16+ dev server:
- 1. Start it: `npm run dev`
- 2. Confirm Next.js 16+ (the `/_next/mcp` endpoint only exists there)
- 3. Verify it started without errors
- `browser_eval` and `nextjs_docs` work without a dev server.
- ## Local Development
- ```bash
- git clone https://github.com/vercel/next-devtools-mcp.git
- cd next-devtools-mcp
- pnpm install
- pnpm build
- ```
- Point your MCP client at the local build:
- ```json
- {
- "mcpServers": {
- "next-devtools": {
- "command": "node",
- "args": ["/absolute/path/to/next-devtools-mcp/dist/index.js"]
- }
- }
- }
- ```
- Or with Codex:
- ```bash
- codex mcp add next-devtools-local -- node dist/index.js
- ```
- See the [Next.js MCP documentation](https://nextjs.org/docs/app/guides/mcp) for how MCP works with Next.js and coding agents.
- ## License
- MIT
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.