Show HN: asyncmcp – Run MCP over async transport via AWS SNS+SQS

by bharatgel • 1 year ago

35 4 1 year 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.

bharatgel2• 1 year ago

Thanks, glad it resonates :)

criticalpudding• 1 year 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!

bharatgel2• 1 year 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?

Show HN: asyncmcp – Run MCP over async transport via AWS SNS+SQS

Related Stories