Is it possible to increase the timeout for remote MCP servers?
{
"id": "mcp_688a1347cbc0819080c5d13e3b48ffef032ff66b23bbc065",
"arguments": "{\"from_airport\":\"LAX\",\"to_airport\":\"LGW\",\"departure_date\":\"2025-10-08\",\"return_date\":null,\"trip_type\":\"one-way\",\"adults\":1,\"children\":0,\"infants\":0,\"seat_class\":\"economy\",\"max_stops\":0,\"airlines\":null,\"max_results\":50}",
"name": "search_flights",
"server_label": "google-flights-mcp",
"type": "mcp_call",
"error": {
"type": "mcp_protocol_error",
"code": 408,
"message": "Timed out while waiting for response to ClientRequest. Waited 60.0 seconds."
}
}
I’m even correctly sending ping events to avoid timeouts.
< HTTP/2 200
< cache-control: no-cache, no-transform
< content-type: text/event-stream
< x-accel-buffering: no
< date: Wed, 30 Jul 2025 14:17:46 GMT
< server: Google Frontend
< alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
<
: ping - 2025-07-30 14:18:01.751610+00:00
: ping - 2025-07-30 14:18:16.754353+00:00
: ping - 2025-07-30 14:18:31.755988+00:00
: ping - 2025-07-30 14:18:46.757559+00:00
: ping - 2025-07-30 14:19:01.759795+00:00
: ping - 2025-07-30 14:19:16.760682+00:00
: ping - 2025-07-30 14:19:31.762235+00:00
: ping - 2025-07-30 14:19:46.763671+00:00
: ping - 2025-07-30 14:20:01.765499+00:00
: ping - 2025-07-30 14:20:16.767116+00:00
: ping - 2025-07-30 14:20:31.767979+00:00
: ping - 2025-07-30 14:20:46.769648+00:00
: ping - 2025-07-30 14:21:01.771366+00:00
: ping - 2025-07-30 14:21:16.773088+00:00
: ping - 2025-07-30 14:21:31.774390+00:00
: ping - 2025-07-30 14:21:46.775819+00:00
: ping - 2025-07-30 14:22:01.777862+00:00
: ping - 2025-07-30 14:22:16.778754+00:00
: ping - 2025-07-30 14:22:31.780185+00:00
: ping - 2025-07-30 14:22:46.780742+00:00
: ping - 2025-07-30 14:23:01.782426+00:00
: ping - 2025-07-30 14:23:16.783595+00:00
: ping - 2025-07-30 14:23:31.785439+00:00
: ping - 2025-07-30 14:23:46.786441+00:00
: ping - 2025-07-30 14:24:01.788368+00:00
: ping - 2025-07-30 14:24:16.791935+00:00
: ping - 2025-07-30 14:24:31.793923+00:00
: ping - 2025-07-30 14:24:46.799441+00:00
: ping - 2025-07-30 14:25:01.801595+00:00
event: message
data: {"jsonrpc":"2.0","id":1,"result":{"content":[{"type":"text","text":"{\"current_price\":\"typical\",\"flights\":[{\"is_best\":true,\"departure\":\"11:37\",\"arrival\":\"14:39\",\"duration\":\"6 hr 2 min\",\"stops\":0,\"flight_date\":\"2025-08-15\",\"segments\":[{\"departure\":\"11:37\",\"arrival\":\"14:39\",\"duration\":\"6 hr 2 min\",\"name\":\"Frontier\",\"flight_number\":\"F9 2503\",\"departure_airport\":\"JFK\",\"arrival_airport\":\"LAX\",\"aircraft\":\"Airbus A321neo\",\"airline_code\":\"F9\",\"departure_date\":\"2025-08-15\",\"arrival_date\":\"2025-08-15\",\"seat_pitch\":\"28 inches\"}],\"price\":179.0,\"key\":\"2025-08-15-JFK-F92503-LAX\"},{"is_best":false,"departure":"16:39","arrival":"00:10","duration":"10 hr 31 min","stops":1,"flight_date":"2025-08-15","segments":[{"departure":"16:39","arrival":"20:02","duration":"6 hr 23 min","name":"Alaska","flight_number":"AS 114","departure_airport":"JFK","arrival_airport":"SFO","aircraft":"Boeing 737MAX 9 Passenger","airline_code":"AS","departure_date":"2025-08-15","arrival_date":"2025-08-15","seat_pitch":"31 inches"},{"duration":"2 hr 33 min","name":"layover"},{"departure":"22:35","arrival":"00:10","duration":"1 hr 35 min","name":"United","flight_number":"UA 1660","departure_airport":"SFO","arrival_airport":"LAX","aircraft":"Boeing 737","airline_code":"UA","departure_date":"2025-08-15","arrival_date":"2025-08-16","seat_pitch":"30 inches"}],"arrival_time_ahead":"+1","price":541.18,"key":"2025-08-15-JFK-AS114-SFO-LAYOVER2H33M-SFO-UA1660-LAX"}]}},"isError":false}}
I’m using o3-2025-04-16 with Azure OpenAI. Anthropic API’s MCP client does not seem to have this problem.