I upgraded kiro IDE from version 0.12.333 to 1.0.89 (win32-x64) and all my MCP servers stop to connect. After some troubleshooting I saw a change on mcp.json on the 333 version. Prior to the upgrade, the "timeout" parameter was defined in seconds, whereas after the upgrade, it is defined in milliseconds. Since there is no unit specified after the numeric value (e.g., timeout=180), the MCPs stop functioning upon upgrading the version. As an improvement, I suggest adding a unit indicator after the number—such as "s" for seconds, "ms" for milliseconds, or leaving it blank for the default unit (seconds)—meaning timeout=180s would be equivalent to 180, which in turn would equal 180000ms. This approach maintains backward compatibility while providing greater granularity for newer versions.
I upgraded kiro IDE from version 0.12.333 to 1.0.89 (win32-x64) and all my MCP servers stop to connect. After some troubleshooting I saw a change on mcp.json on the 333 version. Prior to the upgrade, the "timeout" parameter was defined in seconds, whereas after the upgrade, it is defined in milliseconds. Since there is no unit specified after the numeric value (e.g.,
timeout=180), the MCPs stop functioning upon upgrading the version. As an improvement, I suggest adding a unit indicator after the number—such as "s" for seconds, "ms" for milliseconds, or leaving it blank for the default unit (seconds)—meaningtimeout=180swould be equivalent to180, which in turn would equal180000ms. This approach maintains backward compatibility while providing greater granularity for newer versions.