{"version":"2.1.307","anchor":"mcp-connect-timeouts-can-now-be-reported-as-suspended","canonical_anchor":"mcp-connect-re-dials-after-sleep-or-clock-change","heading":"MCP connections report sleep, clock changes and a locked credential store","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/mcp-connect-timeouts-can-now-be-reported-as-suspended","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### MCP connections report sleep, clock changes and a locked credential store\n\nMCP server connections now recognise a sleep or clock change during connecting and retry, and report when stored credentials cannot be read\n\n**Unclear.** What makes Claude Code treat a timeout as a suspension is not settled.\n\n**What**\n\nMCP servers are add-on programs that give Claude Code extra tools. Two new connection error codes, `CONNECT_SUSPENDED` and `CREDENTIAL_STORE_UNAVAILABLE`, sit next to `CONNECT_TIMEOUT`.\n\n- Suspended connects: when a connection times out because your computer went to sleep or its clock changed while connecting, Claude Code now reports it as suspended rather than a plain timeout. The message reads: 'MCP server \"...\" connection timed out. Your computer went to sleep or its clock changed while connecting.' Claude Code then reconnects a limited number of times, and the usual failure bookkeeping for plugin servers is skipped. Before, this counted as an ordinary timeout and the normal failure path always ran. This path sits behind `tengu_mcp_connect_suspend_redial`, and the existing timeout retry setting `tengu_mcp_connect_timeout_retry` still falls back to true; nothing has been read about either.\n\n- Credential store unavailable: a new error is raised when an MCP server's saved credentials cannot be read, or were read only after a request had already gone out without them, so the request did not run. On macOS the message suggests unlocking the keychain.\n\n**Why**\n\nOpening a laptop after sleep is less likely to leave MCP servers failed after a false timeout, and a locked keychain now shows a clear fix instead of an unexplained login failure.\n\n- Flag `tengu_mcp_connect_timeout_retry`: Not enough to say (read for one account on one subscription tier against v2.1.307; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}