# MCP Server: Configurable Start Timeouts and Asynchronous Loading In the future, MCP Server initialization can be configured via the environment variable ∀MCP_TIMEOUT∀. The MCP Server now starts without blocking the main application startup. This modification addresses two important operational needs in enterprise environments: The ∀MCP_TIMEOUT variable provides fine-grained control over the maximum wait time for boot time, which is particularly useful in environments with fluctuating network or resource availability. In contrast, asynchronous loading decouples MCP Server startup from the critical path of the application, which reduces startup times and improves availability. For deployment teams, this offers greater flexibility in configuration and error handling. Compliance managers benefit from improved control and predictable system behavior. This enables engineers to implement more reliable and resilient systems, particularly in diverse environments with different latency characteristics.
Claude Code Changelog