MCP HTTP as optional, and IDE tool passing

[jwflicker]

So when the IDE has more tools beyond read/write to editor that it would like the agent to have access to (read compilation errors, read console, read editor annotations, ...) MCP seem like a good format to pass these tools through to the agent. To get data out of the IDE Process though MCP over HTTP or SSE seems like the direct way, but these are optional for ACP agents to support. We could create a STDIO MCP that proxies the content of an HTTP MCP i suppose.

What are the thoughts behind making HTTP MCP optional but STDIO required.
Is there another mechanism for passing IDE tools that i'm missing.