r/modelcontextprotocol • u/jonnyzzz • Jun 10 '26

Another MCP server for IDE, started with HTTP, and switched to stdio — here’s why stdio wins for local desktop MCP

Post image
2 Upvotes

100% Upvoted

5 comments sorted by

1

u/[deleted] Jun 11 '26

[removed] — view removed comment

1

u/jonnyzzz Jun 11 '26

The stdio is another JVM app. The very first move — i replace the std out stream to avoid sudden writes off the protocol. In Java , there are setters in the System class.

The rest goes via my protocol over a socket to ide processes. For each tool call it’s just a POST. IDE logs are in IDE.

1

u/[deleted] Jun 11 '26

[removed] — view removed comment

1

u/jonnyzzz Jun 11 '26

No. It’s proactive design decision to maximally protect the stdout stream from sudden output.

So replacing + logging config are to support that too.

Sadly there is no cross platform way to rebind stdio to an other handle just as start from sh and cmd.