Add logging support to local transport used for proxy #69
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.
Adds support for the
notifications/message
method from the official MCP spec to support sending custom logs to themcpProxy
client, independent of the ones relayed from the server.It is currently used in
connectToRemoteServer
to send information which was only logged via console, so that clients have the ability to display status and react to different scenarios.Using a simple callback from the official SDK in a custom client:
You can see the connection logs reflected in the following output: