Browser MCP Support

[sheng-di]

Please read this first

• Have you read the docs? Agents SDK docs
  YES

• Have you searched for related issues? Others may have had similar requests
  YES

Describe the feature

Currently, when trying to use MCPServerStreamableHttp in a browser environment, the class is just an empty stub and throws an error:

Method not implemented

Expected behavior
MCPServerStreamableHttp should have a working implementation in the browser, similar to the Node.js side, enabling browser clients to initiate and consume streaming requests/responses.

Why this is important

Allows building rich web-based clients without resorting to server-side proxies.
Ensures feature parity between Node.js and browser environments.
Improves developer experience for frontend-heavy MCP integrations.

[seratch]

Thanks for sharing this feedback! In theory, connecting to remote MCP servers should work, though it’s generally not recommended to handle the authorization header on the browser frontend. We’re fine with updating the browser shims to support Streamable HTTP and SSE in the near future if they work without any issues.