Connect Next.js DevTools MCP to Codex
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
- Codex 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 Codex
Add it from the terminal
Saves the server to
~/.codex/config.toml, so it works in every project.Terminal codex mcp add next-devtools -- npx -y next-devtools-mcp@latestOr edit the config file
Add this to
~/.codex/config.toml.~/.codex/config.toml [mcp_servers.next-devtools] command = "npx" args = ["-y", "next-devtools-mcp@latest"]Step 2: Check it's connected
Terminal codex mcp listIn a Codex session, run
/mcpto see connected servers and their tools.Step 3: Try a first request
Ask Codex something that only works with Next.js DevTools MCP connected:
Say to Codex 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
- Codex reads
~/.codex/config.toml. A project.codex/config.tomlis only read in projects you have trusted. - Codex doesn't expand
~or environment variables incommand. Use a full path in the config file. - Servers that need a sign-in: run
codex mcp login <name>.





