| ▲ | rco8786 2 hours ago |
| > With the 2026-07-28 release, a remote MCP server is now no different from any other HTTP workload Good. Introducing a bespoke new protocol was one of the more bone-headed things MCP did on initial release. |
|
| ▲ | colingauvin an hour ago | parent | next [-] |
| It's unreal how bad the initial rollout was between HTTP/streaming and stdio, bearer auth and OAuth. Virtually every client/MCP server pair had a different portion of that matrix implemented. |
| |
| ▲ | ihuman 20 minutes ago | parent [-] | | Is stdio being deprecated? I couldn't tell from this page | | |
| ▲ | amluto 9 minutes ago | parent [-] | | The prose on the page is very unclear. My best interpretation is that they want to continue supporting stdio but that they don’t want it to be its own special protocol. The obvious way to do that would be to speak ordinary HTTP (version 1.1? 2?) over stdio and to use the MCP-over-HTTP protocol over the resulting HTTP transport. This would be more complex to implement for a simple server, but it’s not exactly difficult. | | |
| ▲ | Gormo 4 minutes ago | parent [-] | | Not everyone is on board with the idea of HTTP being the exclusive universal IPC bus. |
|
|
|
|
| ▲ | Jhater an hour ago | parent | prev [-] |
| [dead] |
