Skip to content

Conversation

bendvc
Copy link
Contributor

@bendvc bendvc commented Aug 12, 2025

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?

  • You can only use the MCP server locally, these cannot be run remotely.
  • Complications with logging. Since stdio is use for the communication channel between the client (cursore ide) and the server, we cannot use logging that is based on console.log since it uses stdio 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?

  • One downside is that we can't have a single cursor configuration to run the server and communicate with it. When it comes to remote mcp servers (even if they are running locally) the responsibility or starting that server is on the developer. This is what the cursor configuration looks like:
{
  "mcpServers": {
    "pwa-kit": {
      "url": "http://localhost:3001/mcp",
      "env": {
        "PORT": "6001"
      }
    }
  }
}
  • A plus from not using the stdio is that there is no limitation on using it for logging. So we don't have to use a custom logger with file creation, jsut console log (or use a wrapper to filter by level) and you are good to go. This will work well in production environments where we might want to pipe those raw logs to an external system like log center.
  • Generally speaking doing logging like this is more conventional and more widely understood.
  • This might have better integration in terms of analytic data tracking.

What can't we log?

  • User prompts. These sanitized and not made available to the MCP server.

@bendvc bendvc requested a review from a team as a code owner August 12, 2025 18:00
@cc-prodsec
Copy link
Collaborator

cc-prodsec commented Aug 12, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants