Based on available information, while there is no direct reference to increasing the timeout specifically for

ClientRequest

in relation to the

mcp.shared.exceptions.McpError

in the knowledge base, several relevant timeout configuration options exist at both the LiveKit MCP integration level and in related libraries: • MCPServer configuration: The

client_session_timeout_seconds

parameter can be set when initializing an

MCPServer

instance. This defines timeouts used when creating

ClientSession

objects . • MCPServerHTTP configuration: This offers a

timeout

parameter for HTTP requests as well as

client_session_timeout_seconds

. • PSRPC client libraries: There are client-side timeout configuration options . • RPC methods (SDKs): Many client SDKs offer configurable timeouts, such as

responseTimeoutMs

for

performRpc

calls (defaults to 10s, but configurable) . If your usage involves

MCPServer

or

MCPServerHTTP

, try increasing the relevant timeout parameters during initialization. If your timeout originates elsewhere, check your client library or SDK for request timeout configuration options. The specific

mcp.shared.exceptions.McpError: Timed out while waiting for response to ClientRequest

may require adjusting timeouts at the MCP client or library level if it is not directly controlled by LiveKit's MCP integration options. If you can provide details about: I can offer more targeted guidance on how and where to increase the timeout duration. Sources: client.go | Runtime/Scripts/Rpc.cs | lib/src/types/rpc.dart | RPC | LiveKit Docs | livekit-agents/livekit/agents/llm/mcp.py | mcp/agent.py