Next.js DevTools MCP

Connect your agent to a running Next.js dev server — live errors, routes, logs.

Before you connect: what this server would do

A preview derived from this server’s definition — not a live run. Nothing runs and no key is sent until you connect. You run this server on your own machine — FindAgent never runs it.

Tools it can use (4)

nextjs_index
Discover running Next.js dev servers and list their runtime tools.
nextjs_call
Call a runtime tool on a discovered dev server.
nextjs_docs
Point the agent at version-accurate docs inside node_modules.
browser_eval
Point the agent at the agent-browser CLI.

What FindAgent checked

It passed an automated security scan and a human review before it was published here.
You run this server yourself, so FindAgent’s run-time protections — the prompt-injection deny-list on what you send, the secret-leak scan on every result, the credential-to-host binding, the approval gates — do not apply to what you send or receive here.

How FindAgent keeps servers safe

Run locally

This MCP server runs on your own machine — FindAgent only points you at it. Run the command below, then add it to your MCP client. Nothing is hosted or proxied on our side.

terminal

npx -y next-devtools-mcp@latest

Add it to your MCP client

Paste this into your client config (e.g. claude_desktop_config.json or a Cursor mcp.json), then restart the client.

mcp client config

{
  "mcpServers": {
    "next-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "next-devtools-mcp@latest"
      ]
    }
  }
}

View the source repository