[🧱 MCP Server Tool] [Spike] Add logging mechanism for analytics reporting. #3068
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.
Description
This PR is part of the following spike package here 👉🏻 https://salesforce.quip.com/BUpHABtA65Ce
In this PR we explore how we might shift our current implementation of the MCP server to be more flexible by replacing the current
stdio
transport layer and migrate the sever to use a streamable http layer.What are some of the limitation of using a stdio transport layer?
console.log
since it usesstdio
and would interfere with it. This make development a little more brittle because developers can't use console.log and instead have to look at a separate file created in a location create by us.What changes with Http Streaming support?
What can't we log?