next-devtools

next-devtools is an MCP server for Claude Code, Codex, Cursor, Gemini CLI, OpenCode from vercel/microfrontends. Its token cost is not measured, scanned A, a copy of next-devtools, MIT.

A local MCP server that provides development tools for Next.js applications. It runs through the next-devtools-mcp npm package.

In plain words
What is it for?
Use it in a Next.js development environment when you need to configure the listed local development-tools server.
Why use it?
It provides a way to run Next.js development tools locally through the MCP setup.

MCP server for Claude CodeCodexCursorGemini CLIOpenCode ✓ vendor

Written for no agent in particular: it speaks MCP, so any client can run it. Also seen: listed in a Claude config.

Good fit Use it in a Next.js development environment when you need to configure the listed local development-tools server.

Compare 6 mcp servers from other repositories ↓
Install with agentmods
npx agentmods add mcp/vercel/microfrontends/next-devtools
About the project

vercel/microfrontends is a library for splitting a large web application into independently developed applications called microfrontends. It supports microfrontend setups using frameworks and tools including Next.js, SvelteKit, React Router, Vite, and React, including gradual migrations and local development.

vercel/microfrontends · 45 stars · on GitHub · vercel.com

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/vercel/microfrontends

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for next-devtools

README.md
[![agentmods](https://agentmods.dev/badge/mcp/vercel/microfrontends/next-devtools/github.svg)](https://agentmods.dev/mcp/vercel/microfrontends/next-devtools)
Your own site
<a href="https://agentmods.dev/mcp/vercel/microfrontends/next-devtools"><img src="https://agentmods.dev/badge/mcp/vercel/microfrontends/next-devtools/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for next-devtools

Your own site · 80×15
<a href="https://agentmods.dev/mcp/vercel/microfrontends/next-devtools"><img src="https://agentmods.dev/badge/mcp/vercel/microfrontends/next-devtools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Security

Grade A, and why

next-devtools scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to next-devtools — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.mcp.json · 9 lines

What it actually says

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

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 9 lines scan A c81a8ba90c8a

Subscribe to this mod's changes

next-devtools is an MCP server published in the GitHub repository vercel/microfrontends (45 stars, last pushed 4d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It is 100% identical to next-devtools, differing in 0 lines, and is treated as a copy.