Vercel · Codex
Add the Next.js DevTools MCP server to Codex
Gives coding agents Next.js docs, runtime errors and upgrade helpers for your app.
1. Add the server
Run in your terminal
# ~/.codex/config.toml [mcp_servers.next_devtools] command = "npx" args = ["-y", "next-devtools-mcp"]
Scopes, env vars, OAuth and limits: Codex MCP config guide
2. Sign in
Run codex mcp login <name> to complete OAuth for a remote server. Next.js DevTools runs locally; set any credentials Vercel asks for before starting Codex.
3. Try it
Ask Codex for something Next.js DevTools can do. Gives coding agents Next.js docs, runtime errors and upgrade helpers for your app. Approve the first tool call and check the result before allowing write actions automatically.
- · Each server is a [mcp_servers.<name>] table in config.toml.
- · Use enabled_tools or disabled_tools to keep the tool list short.
FAQ
- How do I add the Next.js DevTools MCP server to Codex?
- Run: # ~/.codex/config.toml …. Run codex mcp login <name> to complete OAuth for a remote server.
- Is this the official Next.js DevTools MCP server?
- Yes. It is published by Vercel as io.github.vercel/next-devtools-mcp in the official MCP registry.
- Does the Next.js DevTools MCP server need an API key?
- It runs locally from a package. See Vercel's docs for any credentials it needs.
Links
Next.js DevTools in other clients
More developer tools for Codex
Built an MCP server? Get it listed everywhere →
Shipping an Android app? Google Play needs 12 testers for 14 days first. Get them with Tester Exchange →
Reviewed Oct 21, 2026. Command generated from the registry record and checked against Codex's documented syntax.