{"version":"2.1.305","anchor":"mcp-server-config-copy-now-also-tracks-reply-server-ownershi","canonical_anchor":"mcp-server-config-copy-now-also-tracks-reply-server-ownershi","heading":"Copied MCP server settings keep their built-in status","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/mcp-server-config-copy-now-also-tracks-reply-server-ownershi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Copied MCP server settings keep their built-in status\n\nWhen Claude Code copies an MCP server's settings, the copy is now recognised as built-in only if the original was\n\n**What**\n\nAn MCP server is a separate program that gives Claude extra tools. Claude Code keeps track of which servers are its own. When it copies a server's settings, the copy is now treated as one of its tool servers only if the original was. It does the same for a second group, its reply servers.\n\nBefore, it decided this from the type of server and tracked only tool servers.\n\n**Why**\n\nThis fixes how Claude Code recognises its own MCP servers after their settings have been copied.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}