On Windows, StdioClientTransport calls taskkill and triggers visible cmd windows #420

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

JesseCol opened this issue May 15, 2025 · 0 comments

Labels

bug

JesseCol commented May 15, 2025

Describe the bug
When a StdioClientTransport shuts down, and the server-side process is still alive, MCP calls taskkill here.

04 ModelContextProtocol!ModelContextProtocol.Utils.ProcessHelper.RunProcessAndWaitForExit
05 ModelContextProtocol!ModelContextProtocol.Utils.ProcessHelper.KillTree
06 ModelContextProtocol!ModelContextProtocol.Protocol.Transport.StdioClientTransport.DisposeProcess
07 ModelContextProtocol!ModelContextProtocol.Protocol.Transport.StdioClientSessionTransport.CleanupAsync

When it does this, it triggers a visible cmd window on the user's machine.

I believe we can fix this by setting ProcessStartInfo.CreateNoWindow = true.

To Reproduce
I believe you just need to use STDIO transport, and close it on the client side.

Expected behavior
I expect taskkill to run without popping up any windows.

The text was updated successfully, but these errors were encountered:

JesseCol added the bug label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.

Alternative Proxies:

Alternative Proxy