{"version":"2.1.317","anchor":"plugin-mcp-copies-re-check-and-plugincandidates","canonical_anchor":"plugin-mcp-copies-re-check-and-plugincandidates","heading":"Plugin MCP server copies are now re-checked","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/plugin-mcp-copies-re-check-and-plugincandidates","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Plugin MCP server copies are now re-checked\n\nClaude Code now re-checks the MCP server copies that plugins provide, and loads a session owner from saved transcripts\n\n**What**\n\nPlugins are add-ons that extend Claude Code. Some of them provide MCP servers, which connect Claude Code to outside tools. Claude Code keeps copies of these servers.\n\n- Copy re-check: a new step re-checks these plugin copies and applies any differences under the reason `plugin_copy_recheck`. If the re-check fails, Claude Code logs \"plugin copy re-check failed, its copies wait for the next plugin diff\" and deals with them on the next plugin update.\n\n- Wider scope: a difference can now be scoped to a set of copies, and plugin candidates are passed into the step that brings servers back in line.\n\n- Session owner: separately, a `sessionOwner` field (`sessionOwners` for several) is now loaded from transcripts when a full conversation log is loaded.\n\n**Why**\n\nIn practice, MCP servers provided by plugins are checked again outside the usual update moment. A failed check is not fatal, because the copies are simply handled at the next plugin update.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}