modelcontextprotocol / modelcontextprotocol/csharp-sdk
Streamable HTTP server support under .NET Framework
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.5k
- Forks
- 814
- Avg merge
- 9d 19h
- Merged PRs (30d)
- 4
Description
The previous issue got turned into a discussion and became off-topic to my own issue. I'd like to ask the following question, based on the fact that ModelContextProtocol supports .NET Standard 2.0 and still contains classes and methods for Streamable HTTP servers (e.g StreamableHttpServerTransport):
What is currently stopping .NET Framework from getting Streamable HTTP server support? I see no reason why it is held back for .NET Framework considering the transport class is not. Even a SSE fallback (proven to work on .NET Framework) would be acceptable since it is defined by the MCP specs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the ModelContextProtocol target frameworks and the StreamableHttpServerTransport implementation to determine which .NET Framework constraint prevents server support. The issue mentions no specific files or tests; done would require either implementing supported Streamable HTTP or SSE fallback support, or documenting the concrete blocker and required scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100