Connect Next.js DevTools MCP to Gemini CLI
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
- Gemini CLI 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 Gemini CLI
Add it from the terminal
Run this in your project folder. It saves the server to the project's
.gemini/settings.json.Terminal gemini mcp add next-devtools npx -- -y next-devtools-mcp@latestOr edit the config file
Add this to
.gemini/settings.jsonin your project, or to~/.gemini/settings.jsonto use it in every project..gemini/settings.json { "mcpServers": { "next-devtools": { "command": "npx", "args": [ "-y", "next-devtools-mcp@latest" ] } } }Step 2: Check it's connected
Terminal gemini mcp listIn a Gemini CLI session, run
/mcpto see each server, its status and its tools.Step 3: Try a first request
Ask Gemini CLI something that only works with Next.js DevTools MCP connected:
Say to Gemini CLI 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
- Since June 2026, Gemini CLI works with a paid Gemini API key or an enterprise licence. If you signed in with a personal Google account, use Google Antigravity instead.
gemini mcp addsaves to the project's.gemini/settings.jsonby default. Add--scope userto save it to~/.gemini/settings.jsonfor every project.- Local servers only show as connected in folders you trust. Run
gemini trustin the project folder. - Gemini CLI hides environment variables that look like secrets from servers unless the server's
envblock lists them.






