{"version":"2.1.248","anchor":"duplicate-mcp-server-entries-merged-correctly","canonical_anchor":"duplicate-mcp-server-entries-merged-correctly","heading":"Duplicate MCP server entries merged correctly","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/duplicate-mcp-server-entries-merged-correctly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Duplicate MCP server entries merged correctly\n\nThe same MCP server defined in two config files now merges correctly.\n\n**What**\n\nWhen two configuration sources define the same MCP server, the merge step was writing into the wrong place and comparing the wrong entry's passthrough tools. It now builds the merged entry and only stores it when something actually changed.\n\n**Evidence**\n\n`return d === o ? t : t.set(r.name, d);`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}