Unverified50% confidenceFactExact time
The client_session_timeout_seconds parameter of MCPServerStreamableHttp controls the maximum time the underlying MCP session waits for a response to a single request, not the total duration of the entire Agent run; the Agent's Runner.run has its own run-level timeout, the two are at different levels and do not override each other.
1
Sources
50%
Confidence
Long-term
Relevance
10/12/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedRequest timeouts can be configured via McpClientCustomizer — for example, if no response is received within 30 seconds, the MCP Server will automatically disconnect78% similarUnverifiedPush mode reuses MCP's existing stream mechanism to establish a long-lived event stream between the client and server, suitable for low-latency, high-throughput scenarios.71% similarUnverifiedMCP allows Agents to pull data in real time on demand rather than relying on pre-scheduled batch synchronization, but because it lacks the cleansing buffer layer of ETL, it places higher demands on the quality of data returned by MCP servers.70% similarUnverifiedAfter mcp.run() is called, the server begins listening on standard input, waiting for a model to connect and make calls.70% similarUnverifiedMCP introduced the concept of MCP Tasks, supporting long-running asynchronous tasks that may take minutes, hours, weeks, or even months.70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1008306API
curl https://kongchang.com/api/v1/knowledge/claims/1008306MCP
get_claim(id=1008306)