Next.js DevTools (local) logo

Next.js DevTools (local)

Beta

Vercel's Next.js DevTools server relays live runtime errors, routes and logs from Next.js development servers to the agent.

  • Developer Tools
  • Local
Runs
On the developer's Mac
Launched with
npx
Platform
macOS
Publisher
Vercel

How it works

Every agent request passes through Ferentin policy before it reaches Next.js DevTools (local).

It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y next-devtools-mcp.

Ferentin's endpoint agent finds Next.js DevTools (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.

  1. AI agentAsks for something
  2. Ferentin policies
  3. Next.js DevTools (local) MCP serverRuns on the developer's Mac
  4. Governed resultChecked, logged, returned

About Next.js DevTools (local)

Vercel's Next.js DevTools server relays live runtime errors, routes and logs from Next.js development servers to the agent.

Frequently asked about Next.js DevTools (local)

How do I connect Next.js DevTools (local) to Ferentin?
Enroll your Macs with the Ferentin endpoint agent, then add Next.js DevTools (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
Is the Next.js DevTools (local) integration generally available?
The Next.js DevTools (local) integration is currently beta on Ferentin.