{"version":"2.1.259","anchor":"sdk-mcp-server-timeout-changes-on-already-registered-servers","canonical_anchor":"sdk-mcp-server-timeout-changes-on-already-registered-servers","heading":"SDK MCP server timeout changes on already-registered servers are ignored with a warning","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/sdk-mcp-server-timeout-changes-on-already-registered-servers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### SDK MCP server timeout changes on already-registered servers are ignored with a warning\n\nRe-sending initialize with a different timeout for a registered SDK MCP server now warns that the change is ignored.\n\nIf `initialize` is re-sent specifying a different timeout for an SDK MCP server that's already registered, Claude Code now logs a warning that the timeout change is ignored until the server is removed and re-added, rather than silently applying or dropping the new value.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}