{"version":"2.1.238","anchor":"mcp-servers-can-connect-lazily-from-a-cached-entry","canonical_anchor":"mcp-servers-can-connect-lazily-from-a-cached-entry","heading":"MCP servers can connect lazily from a cached entry","tier":"soon","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/mcp-servers-can-connect-lazily-from-a-cached-entry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### MCP servers can connect lazily from a cached entry\n\nTool calls to a remembered MCP server could dial it on demand, but the cache behind it is off.\n\n**What**\n\nA tool call to a server that exists only as a cached discovery entry can now dial it on demand rather than failing, and `\/mcp` re-authentication clears the cached entry before reconnecting. Both depend on the MCP discovery cache, enabled only by setting `MCP_DISCOVERY_CACHE` to true or by a server value, and off otherwise.\n\n**Details**\n\n- Client-state updates carry an attempt counter and are discarded, with remote connections detached and closed, when the signed-in account moved underneath them.\n- Reconnect callbacks, tool-list-changed handlers and initial-connect retries all re-check that counter before applying anything.\n- The `cached` client type itself only exists when the cache is on.\n\n**Evidence**\n\n`mcp_call lazy connect`\n\n- Area: MCP\n- Names: `MCP_DISCOVERY_CACHE`, `\/mcp`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}