Yes That's true. The original MCP server recommend stdio, streaminghttp and other formats and earlier month in 2026, they recommend switch to streaminghttp way which is easier to support higher QPS and distinguish request using individual session ids and multiple connections (But the implementation always give wrong MCP request error).
And now they provide a single HTTP request which make the access easier. Probability because the growing market of skills and clis direct access instead of MCP tax (long prompts) to complete for Agents access plugin market. So basically it might be the results of competition from other alternatives!
The desire to push back into MCP highlights one of the primary tensions with AI agents in my mind. For an AI agent to be useful it needs to have broad access. For an AI agent to be safe it either needs limited access or perfect alignment. And perfect alignment doesn't currently exist.
Yes That's true. The original MCP server recommend stdio, streaminghttp and other formats and earlier month in 2026, they recommend switch to streaminghttp way which is easier to support higher QPS and distinguish request using individual session ids and multiple connections (But the implementation always give wrong MCP request error). And now they provide a single HTTP request which make the access easier. Probability because the growing market of skills and clis direct access instead of MCP tax (long prompts) to complete for Agents access plugin market. So basically it might be the results of competition from other alternatives!
The desire to push back into MCP highlights one of the primary tensions with AI agents in my mind. For an AI agent to be useful it needs to have broad access. For an AI agent to be safe it either needs limited access or perfect alignment. And perfect alignment doesn't currently exist.