MCP Client Connection Handling on A2A Server

[signoredems]

My implementation includes a Strands A2A server that utilizes tools from a remote MCP server that uses SSE (FWIW, this is the Atlassian MCP server but I'm not sure that detail matters). The A2A Server must use multiple MCP tools when a client is interacting with it, utilizing the results from one tool call to make subsequent ones, but likely has long periods of time in between client connections. What is the correct way to manage connections in this scenario? I can go into how I handle this currently but I'd rather leave it open-ended in the hopes that there is a straightforward way of implementing this that I've totally missed.

Note: I hopeful that I could just use the improved MCP DX feature but I don't see that in the roadmap.