mcp: allow injecting custom streams in StdioTransport #465
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.
Previously,
StdioTransport
was hardcoded to useos.Stdin
andos.Stdout
, making it difficult to test transport behavior with controlled input/output. With this change, users can inject custom streams (likeio.Pipe()
) for testing while maintaining backward compatibility.This change modifies the
Connect
method to check the fields, defaulting back to the standard streams as defaults if nil.