René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Implement asynchronous task execution with result retrieval after connection loss","articleBody":"Currently, the MCP SDK doesn't provide a built-in mechanism for asynchronous task execution where the client can retrieve results after a connection loss. This feature would be valuable for long-running tasks or scenarios where network stability is a concern.\n\nFeature request:\nImplement a way for MCP Client to submit an asynchronous task to MCP Server, disconnect, and later retrieve the task execution results.\n\nProposed workflow:\n1. MCP Client submits a task to MCP Server\n2. MCP Server returns a unique task ID\n3. MCP Client can disconnect\n4. MCP Server continues processing the task\n5. MCP Client can reconnect later and query the task status/results using the task ID\n\nPossible implementation ideas:\n- Add a new API endpoint for submitting async tasks\n- Implement a task queue on the server side\n- Add a method to query task status and retrieve results\n- Consider using a persistent storage solution for task results\n\nThis feature would enhance MCP's capabilities for handling long-running tasks and improve resilience in unstable network conditions.\n\nAny thoughts or suggestions on how to best implement this feature would be appreciated.","author":{"url":"https://github.com/istarwyh","@type":"Person","name":"istarwyh"},"datePublished":"2025-05-21T11:36:34.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/769/python-sdk/issues/769"}