[Feature Request] Tunable timeouts on clients

[amikhail48]

There are a couple hardcoded client timeouts used for both initialization and waiting on responses:

• stdio server response timeout: https://github.com/hkr04/cpp-mcp/blob/main/src/mcp_stdio_client.cpp#L823
• sse initialization timeout: https://github.com/hkr04/cpp-mcp/blob/main/src/mcp_sse_client.cpp#L62

please expose those as configurable parameters to users.

Here are logs from a practical example, a stdio client that times out setting up this node package holds up the entire app for an additional 40 seconds:

2025-11-06 09:52:39 [INFO] Creating MCP stdio client for command: npx -y @smithery/cli@latest run @isdaniel/mcp_weather_server --key 18791e1f-3e01-4754-90c6-0fa6a646541c --profile horizontal-cow-Oc9ZrR
2025-11-06 09:52:39 [INFO] Initializing MCP stdio client...
2025-11-06 09:52:39 [INFO] Starting server process: npx -y @smithery/cli@latest run @isdaniel/mcp_weather_server --key 18791e1f-3e01-4754-90c6-0fa6a646541c --profile horizontal-cow-Oc9ZrR
2025-11-06 09:52:39 [INFO] Read thread started
2025-11-06 09:52:40 [INFO] Server process started successfully, PID: 35307
2025-11-06T17:53:00.612Z [Runner] Error: Request timed out: TimeoutError: The operation was aborted due to timeout
2025-11-06 09:53:00 [WARNING] Pipe closed by server
2025-11-06 09:53:00 [INFO] Read thread stopped
2025-11-06 09:53:40 [ERROR] Initialization failed: Timeout waiting for response
2025-11-06 09:53:40 [INFO] Stopping server process...
2025-11-06 09:53:40 [INFO] Sending SIGTERM to process: 35307
2025-11-06 09:53:40 [INFO] Server process stopped  

[amikhail48]

or perhaps the right approach may be to just bail sooner if the pipe is closed or the read thread is stopped. Let me know what you think