Skip to content

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

chore(web): add Next devtools MCP guidance

YeonGyu-Kim851159636b19
diff --git a/packages/web/.mcp.json b/packages/web/.mcp.json
new file mode 100644
index 00000000..ee5d245d
--- /dev/null
+++ b/packages/web/.mcp.json
@@ -0,0 +1,8 @@
+{
+ "mcpServers": {
+ "next-devtools": {
+ "command": "npx",
+ "args": ["-y", "next-devtools-mcp@latest"]
+ }
+ }
+}
diff --git a/packages/web/AGENTS.md b/packages/web/AGENTS.md
new file mode 100644
index 00000000..c1fc6dd9
--- /dev/null
+++ b/packages/web/AGENTS.md
@@ -0,0 +1,7 @@
+# packages/web Agent Notes
+
+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.
+
+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.