Is stdio being deprecated? I couldn't tell from this page

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 38 minutes ago | parent [-]

Not everyone is on board with the idea of HTTP being the exclusive universal IPC bus.

	▲	amluto 8 minutes ago \| parent \| next [-]
		I’m not really a fan. But if you’re building a protocol that needs to map to HTTP anyway, then maybe using the HTTP binding everywhere is not totally awful. In the flip side: I’m currently designing an AI-adjacent protocol, and it will be able to map to WebTransport, but I don’t plan to define non-WebTransport HTTP bindings unless a very compelling reason appears. The main implementations will not use HTTP at all :)
	▲	pstuart 9 minutes ago \| parent \| prev \| next [-]
		Would you prefer gRPC, thrift, avro, etc... ?
	▲	intrasight 33 minutes ago \| parent \| prev [-]
		Count me as not on board