{"version":"2.1.202","anchor":"mcp-connector-duplicate-entry-merging","canonical_anchor":"mcp-connector-duplicate-entry-merging","heading":"MCP Connector Duplicate Entry Merging","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.202\/e\/mcp-connector-duplicate-entry-merging","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.202","markdown":"### MCP Connector Duplicate Entry Merging\n\nWhen multiple skill manifest entries resolve to the same MCP connector, they are now automatically merged into a single connector entry instead of producing ambiguous `server_ambiguous` errors.\n\n**Details**\n\n- Duplicate entries are merged by unioning their tool lists\n- A warning is emitted: \"[N] manifest entries resolve to connector '[name]' and were merged into one ([M] tools). A viewer with more than one connector named '[name]' gets server_ambiguous on every call until the duplicates are renamed or removed.\"\n- Entries that cannot be resolved (using the `claude_ai_` prefix namespace) are reported as unresolved rather than silently dropped\n\n**Evidence**\n\nConnector dedup logic (search for `\"were merged into one (\"` and `\"server_ambiguous on every call\"`)"}