mcp-canonical-list-redundancy-causes-version-drift

Restating the same MCP server list in multiple files (MEMORY.md, architecture.md, feedback files, session-learnings) causes version drift — e.g., Superpowers version showed as v5.0.1 in plugin-integration.md and v5.0.5 in protocols.md simultaneously. The fix is strict canonicalization: one file owns the authoritative list, all others contain only a pointer reference. For permanent MCPs the canonical home is MEMORY.md § System Pointers.

Related

• sops-architectural-primitive-between-one-off-and-skill
• docker
• graphiti
• salesforce
• 2026-04-04-oracle-001-self-architecture-analysis
• permanent-mcp-list-quadruple-restatement-causes-version-drif
• permanent-mcp-list-must-have-single-canonical-home
• permanent-mcp-count-drift-from-multiple-restatement-location
• mcp-permanent-list-must-have-exactly-one-canonical-home