fix: Expose the MCP child process PID as an accessible property in StdioClientTransport #455
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Expose the MCP child process PID as an accessible property in
StdioClientTransport
Motivation and Context
The stdio transport connects to servers by spawning a process and communicating over stdin/stdout. When debugging a server running via this transport, IDE debuggers require the child process PID to properly attach to the server's Node process.
This change exposes the child process PID through the MCP client SDK, enabling direct debugger attachment without requiring manual PID lookup or additional tooling. This improves the developer debugging experience when working with stdio-based server connections.
How Has This Been Tested?
Added UT and used in sample MCP template
Breaking Changes
No breaking changes
Types of changes
Checklist