Connect Next.js DevTools MCP to Conductor
Vercel's MCP server for Next.js. It connects to your running dev server so agents can read build and runtime errors, routes and logs, and search the Next.js docs.
MCP serverOfficialChecked 2026-11-16
Before you start
- Conductor installed (see its MCP documentation (opens in a new tab)).
- Next.js DevTools MCP is available on macOS, Windows and Linux.
- Needs Next.js 16 or later. Start the dev server (
npm run dev) before the agent connects; it serves the endpoint the MCP server talks to. Error and page tools read from pages open in a browser.
Step 1: Add Next.js DevTools MCP to Conductor
For Claude Code sessions
Saves the server to your Claude Code user settings, so every Conductor workspace gets it.
Terminal claude mcp add --scope user next-devtools -- npx -y next-devtools-mcp@latestFor Codex sessions
Saves the server to
~/.codex/config.toml, which Codex sessions in every workspace read.Terminal codex mcp add next-devtools -- npx -y next-devtools-mcp@latestOr share it with your team
Add this to
.mcp.jsonat the project root and commit it. Claude Code sessions in every workspace on that branch pick it up..mcp.json { "mcpServers": { "next-devtools": { "type": "stdio", "command": "npx", "args": [ "-y", "next-devtools-mcp@latest" ] } } }Or edit Codex's config file
Add this to
~/.codex/config.toml.~/.codex/config.toml [mcp_servers.next-devtools] command = "npx" args = ["-y", "next-devtools-mcp@latest"]Good to know- Start a new session in Conductor after adding a server, so the agent loads it.
Step 2: Check it's connected
Terminal claude mcp listIn a Conductor session, click the plug icon in the composer or run
/mcp-statusto see each server's status.Step 3: Try a first request
Ask Conductor something that only works with Next.js DevTools MCP connected:
Say to Conductor Check my running Next.js dev server for build or runtime errors and explain how to fix the first one.
If it doesn't work
- Conductor has no MCP settings of its own. Claude Code and Codex sessions load the same servers they use outside Conductor.
- Each workspace is a separate git worktree. Servers added with plain
claude mcp addonly apply to the folder you ran it in, so use--scope useror a committed.mcp.json. - Conductor runs on macOS. Environment variables for local servers can go in
.conductor/settings.local.toml, under[environment_variables].






