Closed
Description
Is your feature request related to a problem? Please describe.
VS Code doesn't require the user to specify whether an HTTP MCP server is using streamable HTTP or SSE as its protocol. Yet it Just Works, because VS Code first tries Streamable and then falls back to SSE if that fails.
Yet in this .NET SDK, SseClientTransportOptions.UseStreamableHttp requires the client to know beforehand which one it is. This isn't compatible with sharing mcp.json files between VS and VS Code.
Describe the solution you'd like
Can this library include automatic detection (via trying streamable then falling back to SSE)?
Describe alternatives you've considered
Document how a client should reproduce VS Code behavior, including:
- Which mode a client should try first
- Which API will throw the exception
- What the exception type will be and any distinguishing properties on that exception that we can use to know that it's worth retrying with the other setting.