dual-claude-json-config-drift-detection-via-mcp-list-count

State drift between /home/claude/.claude.json and /root/.claude.json can be detected by running claude mcp list from both user contexts and comparing server counts. A discrepancy (e.g., 8 vs 7) indicates a registration was added to one config but not mirrored. The canonical dual-config rule requires both files to be identical; any jq write to one must be followed by an identical write (via sudo) to the other in the same operation.

Related

• desktop-connector-migration-cascade-requires-four-file-updat
• dual-claude-json-config-parity-required-for-root-sessions
• mcp-dual-config-drift-risk-claude-json
• dual-claude-json-sync-home-and-root-must-be-identical
• dual-claude-json-must-stay-identical-after-mcp-changes
• deferred-queue-dual-path-same-inode
• dual-claude-json-must-stay-in-sync-for-permanent-7
• r-dash-echarts-pnpm-install-required-after-wave3