Add mandatory MCP commit rule to AGENTS.md — all MCP work goes to mcpengine-repo

AGENTS.md

@@ -66,6 +66,31 @@ This keeps identity, memory, and progress backed up. Consider making it private
 - End every reply with a model tag: `· sonnet` or `· opus`
 - This costs ~2 tokens, helps Jake track what's being used
 
+## MCP Work — MANDATORY Commit Rule
+
+**ALL MCP-related work MUST be committed and pushed to `mcpengine-repo/` (`BusyBee3333/mcpengine`).**
+
+This is non-negotiable. The mcpengine repo is the single source of truth.
+
+### What goes where:
+- New MCP server → `mcpengine-repo/servers/{platform-name}/`
+- MCP apps/UI → `mcpengine-repo/servers/{platform-name}/src/apps/` or `ui/`
+- Factory tools → `mcpengine-repo/infra/factory-tools/`
+- Pipeline state → `mcpengine-repo/infra/command-center/`
+- Reviews/evals → `mcpengine-repo/infra/factory-reviews/`
+- Landing pages → `mcpengine-repo/landing-pages/`
+- MCP research/docs → `mcpengine-repo/docs/`
+
+### Workflow:
+1. Can build in workspace for speed (scratch space)
+2. When done: `rsync -a --exclude='node_modules' --exclude='.git' src/ mcpengine-repo/servers/{name}/`
+3. `cd mcpengine-repo && git add -A && git commit -m "{name}: {what}" && git push`
+4. **Never** leave MCP work as loose workspace directories without also syncing to mcpengine
+
+### Also push to individual repos when they exist:
+- GHL → `BusyBee3333/Go-High-Level-MCP-2026-Complete`
+- 30 original servers → `BusyBee3333/{name}-mcp-2026-complete`
+
 ## Discord-specific rule
 - If you ever feel like you lack context in a Discord conversation, **proactively read the past few messages** in that channel using the message tool (action=search or action=read with before/after parameters) before asking for clarification.