Handling MCP Tool Calls That Take Minutes: Client Timeout Practices Explored
Hot_Bee_5451 · reddit · 2026-10-22
A Reddit MCP developer raises a practical engineering problem: the spec has progress notifications and cancellation, and long-running tasks now have an official extension, but docs are unclear on how long each client actually waits before giving up on a tools/call. For tasks like "wait for a human reply" or anything running 5-10 minutes, the options are: return a job id immediately with a separate status tool, stream progress notifications and hope the client keeps the request open, or use the tasks extension. The author also asks which clients actually support tasks so far — Claude Desktop, ChatGPT, Cursor, or others.
More from coding & agent
- Anthropic launches Claude Duet, a proactive agent app powered by Opus 5.5 — testingcatalog · 2026-10-22
- MiniMax M3.1 Flash pairs with SGLang Omni for interruptible real-time voice agents — MiniMax_AI · 2026-10-22
- Routing strongest model every turn is bad design: one route per turn, pin through tools — WirelessLife · 2026-10-22
- v0 adds Slack MCP support: read threads and post updates from your agent — iamsahaj_xyz · 2026-10-22
- Insurer portals blocked their data-center bots, so they moved automation into the user's browser — alex_verem · 2026-10-22
- Chrome DevTools adds Ads panel showing per-script CPU and network cost of ads — gaganghotra_ · 2026-10-22