Contaienrs remain after tool closes

[jgardner04]

Issue Description

When using the mcp-think-tool with the MCP client, the mcp-think-tool containers do not terminate as expected when the MCP client is closed. This behavior is inconsistent with other MCP servers, which terminate properly upon the MCP client's closure.

Steps to Reproduce

1. Add the following configuration to the MCP client:

   "think": {
      "command": "podman",
      "args": ["run", "--rm", "-i", "mcp-think-tool"]
   }

2. Start the MCP client and observe the behavior of the mcp-think-tool container.
3. Close the MCP client.
4. Check if the mcp-think-tool container has terminated.

Expected Behavior

The mcp-think-tool container should terminate automatically when the MCP client is closed.

Actual Behavior

The mcp-think-tool container continues to run even after the MCP client has been closed.

Environment Details

Podman Version (Client):

• Client: Podman Engine
• Version: 5.4.2
• API Version: 5.4.2
• Go Version: go1.24.2
• Built: Wed Apr 2 06:43:09 2025
• Build Origin: brew
• OS/Arch: darwin/arm64

Podman Version (Server):

• Server: Podman Engine
• Version: 5.4.1
• API Version: 5.4.1
• Go Version: go1.23.7
• Git Commit: b79bc8afe796cba51dd906270a7e1056ccdfcf9e
• Built: Mon Mar 10 17:00:00 2025
• OS/Arch: linux/arm64

Additional Context

The output of the mcp-think-tool container is as follows:

Processing request of type ListResourcesRequest
{"jsonrpc":"2.0","id":2771,"result":{"resources":[]}}
Processing request of type ListPromptsRequest
{"jsonrpc":"2.0","id":2772,"result":{"prompts":[]}}

Other MCP servers running in containers terminate as expected when the MCP client is closed. However, this behavior is not observed with the mcp-think-tool.