You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When running MCP tools from Docker, the close doesn't properly terminate the container. It keeps running in the background.
The tools are working correctly. However, because they have to run using -i it keeps running the container.
The main problem is that when the StdioClientTransport .close() is called, it executes this._abortController.abort(), but doesn't terminate the container for some reason. So when my application finishes, it never exits, because the child process is still running.
To Reproduce
Steps to reproduce the behavior:
Create an MCP client and configure a Docker MCP server:
Expected behavior
It should terminate all child processes started by StdioClientTransport. If the process doesn't terminate properly, it should be killed.
Logs
No relevant logs.
Additional context
I am running it on Mac OS Sequoia using the latest version of Docker and the latest version of the library 1.12.0.
The text was updated successfully, but these errors were encountered:
Describe the bug
When running MCP tools from Docker, the close doesn't properly terminate the container. It keeps running in the background.
The tools are working correctly. However, because they have to run using
-i
it keeps running the container.The main problem is that when the
StdioClientTransport .close()
is called, it executesthis._abortController.abort()
, but doesn't terminate the container for some reason. So when my application finishes, it never exits, because the child process is still running.To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should terminate all child processes started by StdioClientTransport. If the process doesn't terminate properly, it should be killed.
Logs
No relevant logs.
Additional context
I am running it on Mac OS Sequoia using the latest version of Docker and the latest version of the library 1.12.0.
The text was updated successfully, but these errors were encountered: