Show HN: asyncmcp – Run MCP over async transport via AWS SNS+SQS (opens in new tab)

(github.com)

35 pointsbharatgel8mo ago4 comments

4 comments

Strongly agree with this approach. Real world task specific LLM query workloads tend to be long lived workflows. They should be brokered and handled rather than wait on.

bharatgelOP8mo ago

Thanks, glad it resonates :)

criticalpudding8mo ago

This is perfect for my use case! I'm building a MCP tool that can take 4~10 minutes to complete, and I'm using exactly what you described in README (having another MCP tool for models to poll results) to solve the async problem, which is not ideal. Hope this gets adopted more widely!

bharatgelOP8mo ago

I'm curious how you're making the polling for results approach work right now? Is it a conditional logic that depends on the result from MCP. Or you let the LLM keep deciding on what to do next?

j / k navigate · click thread line to collapse

4 comments

awsanswers8mo ago

Strongly agree with this approach. Real world task specific LLM query workloads tend to be long lived workflows. They should be brokered and handled rather than wait on.

bharatgelOP8mo ago

Thanks, glad it resonates :)

criticalpudding8mo ago

bharatgelOP8mo ago

I'm curious how you're making the polling for results approach work right now? Is it a conditional logic that depends on the result from MCP. Or you let the LLM keep deciding on what to do next?

j / k navigate · click thread line to collapse