mcp-permanent-list-must-have-exactly-one-canonical-home
The Permanent MCP server list was quadruple-restated across MEMORY.md, feedback_mcp_two_tier_model.md, architecture.md, and session-learnings.md — causing version drift (count said 10 in some files, 11 in others after adding Serena). Single source of truth must be MEMORY.md § System Pointers; all other files must reference it, never restate it. Any addition to the permanent list requires a cascade grep across all 4 locations minimum, with a MEMORY.md update as the authoritative source.
Related
- permanent-mcp-list-quadruple-restatement-causes-version-drif
- permanent-mcp-list-must-have-single-canonical-home
- mcp-canonical-list-redundancy-causes-version-drift
- permanent-mcp-count-drift-from-multiple-restatement-location
- docker
- desktop-connector-migration-cascade-requires-four-file-updat
- mcp-permanent-count-hardens-in-multiple-doc-files