Skip to content

The one and only agent harness for complex codebases. Project memory, planning, execution, and verified completion inside Codex.

chore(web): pin Next devtools MCP version

YeonGyu-Kim6cbe44abf5ad
diff --git a/packages/web/.mcp.json b/packages/web/.mcp.json
index ee5d245d..f874f17e 100644
--- a/packages/web/.mcp.json
+++ b/packages/web/.mcp.json
@@ -2,7 +2,7 @@
"mcpServers": {
"next-devtools": {
"command": "npx",
- "args": ["-y", "next-devtools-mcp@latest"]
+ "args": ["-y", "[email protected]"]
}
}
}
diff --git a/packages/web/AGENTS.md b/packages/web/AGENTS.md
index c1fc6dd9..0ffffbe8 100644
--- a/packages/web/AGENTS.md
+++ b/packages/web/AGENTS.md
@@ -2,6 +2,6 @@
This package is a Next.js 16 app. Before making Next.js-specific code or config changes, read the installed version-matched docs under `node_modules/next/dist/docs/`, starting with `node_modules/next/dist/docs/index.md`.
-The project also enables Next DevTools MCP through `.mcp.json` using `next-devtools-mcp@latest`. When the dev server is running, Next.js 16 exposes its MCP endpoint at `/_next/mcp`; use the MCP server for live route, metadata, logs, and error diagnostics when available.
+The project also enables Next DevTools MCP through `.mcp.json` using the pinned `[email protected]` package. When the dev server is running, Next.js 16 exposes its MCP endpoint at `/_next/mcp`; use the MCP server for live route, metadata, logs, and error diagnostics when available.
Keep the LazyCodex visual surface unchanged unless the user explicitly asks for design changes. Treat `DESIGN.md` as the source of truth for colors, typography, spacing, image behavior, and landing/docs information architecture.