{"version":"2.1.314","anchor":"mcp-task-re-bind-identity-check-changed","canonical_anchor":"mcp-task-re-bind-identity-check-changed","heading":"Changed check for reconnecting an MCP task to its server","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/mcp-task-re-bind-identity-check-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Changed check for reconnecting an MCP task to its server\n\nThe check deciding whether a task can reconnect to its MCP server after the server's setup changed works differently now\n\n**Unclear.** It is not clear which setup changes now allow or block a task from reconnecting.\n\n**What**\n\nAn MCP server is an outside service that gives Claude Code extra tools. A task started with one can later reconnect to it. Before reconnecting, Claude Code checks that the server's setup has not changed. That check used to compare a fingerprint of the setup with a saved one, and now uses a different comparison. When the check fails, the message still says the server was reconfigured to a different transport since the task was created.\n\n**Why**\n\nThis affects when a task may reconnect to its MCP server.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}