{"version":"2.1.293","anchor":"mcp-cached-connect-threads-the-tool-use-id-into-the-connecti","canonical_anchor":"mcp-cached-connect-threads-the-tool-use-id-into-the-connecti","heading":"MCP connection attempts now carry the tool call that started them","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/mcp-cached-connect-threads-the-tool-use-id-into-the-connecti","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### MCP connection attempts now carry the tool call that started them\n\nWhen a tool call makes Claude Code connect to a cached MCP server, the call's id is now passed into the connection attempt\n\n**What**\n\nMCP servers are add-on programs that give Claude Code extra tools. When a tool call, a request to use one of those tools, makes Claude Code connect to a previously used MCP server, the call's id is now handed to the connection attempt. It is cleared once the connection finishes or fails.\n\n**Why**\n\nThis may change how sign-in or follow-up questions during a connection are tied to the tool call that caused them.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}