Skip to content

Connect Next.js DevTools MCP to Zed

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

  • Zed 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.
  1. Step 1: Add Next.js DevTools MCP to Zed

    Add it to your settings

    Run zed: open settings file from the command palette and add this inside the top-level object, next to your other settings.

    ~/.config/zed/settings.json
    {
      "context_servers": {
        "next-devtools": {
          "command": "npx",
          "args": [
            "-y",
            "next-devtools-mcp@latest"
          ]
        }
      }
    }
  2. Step 2: Check it's connected

    Open Settings → AI → MCP Servers. A green dot next to the server means it is running.

  3. Step 3: Try a first request

    Ask Zed something that only works with Next.js DevTools MCP connected:

    Say to Zed
    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

  • Zed reads MCP servers from the context_servers key, not mcpServers. Servers under any other key are ignored.
  • Run zed: open settings file from the command palette to edit your settings.
  • Zed asks before running each tool. Change this with agent.tool_permissions in your settings.