The distributed command is an example of a distributed MCP server.
It forks multiple child processes (according to the -child_ports flag), each
of which is a streamable HTTP MCP server with the 'inc' tool, and proxies
incoming http requests to them.
Distributed MCP servers must be stateless, because there's no guarantee that
subsequent requests for a session land on the same backend. However, they
may still have logical session IDs, as can be seen with verbose logging
(-v).