---
title: "Comment by Hayrullah Kar on \"Architecting Durable MCP Servers in Laravel for Long-Running AI Agents\" | Hashnode"
description: "One detail in section 1 is worth adjusting. MCP is not limited to a blocking request and response. The Streamable HTTP transport can answer a tool call with a S"
url: "https://hashnode.com/posts/architecting-durable-mcp-servers-in-laravel-for-long-running-ai-agents/6ae5c0202b6f7d05044d6501/comment/6ae6f1c312b873a336d03c13"
---

[Discussion](https://hashnode.com/posts/architecting-durable-mcp-servers-in-laravel-for-long-running-ai-agents/6ae5c0202b6f7d05044d6501)

Comment [Architecting Durable MCP Servers in Laravel for Long-Running AI Agents](https://hashnode.com/posts/architecting-durable-mcp-servers-in-laravel-for-long-running-ai-agents/6ae5c0202b6f7d05044d6501)

[Hayrullah Kar](https://hashnode.com/@magesheet)

[Nov 1](https://hashnode.com/posts/architecting-durable-mcp-servers-in-laravel-for-long-running-ai-agents/6ae5c0202b6f7d05044d6501/comment/6ae6f1c312b873a336d03c13)

One detail in section 1 is worth adjusting. MCP is not limited to a blocking request and response. The Streamable HTTP transport can answer a tool call with a Server-Sent Events stream, no WebSockets needed, and the spec has `notifications/progress` for long calls. Your ticket pattern still makes sense behind a proxy with a hard idle timeout.