modelcontextprotocol / modelcontextprotocol/csharp-sdk
Transfer-Encoding=Chunked causes issues with locally run Azure Functions
Open
Nobody has claimed this yet.
bug
needs confirmation
P2
- Dominant language
- C#
- Stars
- 4.5k
- Forks
- 814
- Avg merge
- 9d 19h
- Merged PRs (30d)
- 4
Description
#816 was caused by running the Azure Function locally, as apparently Transfer-Encoding=Chunked doesn't play nice with Python SDK MCP Servers.
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
No files or tests are named. Start by reproducing the locally run Azure Function behavior described in #816 and inspect how Transfer-Encoding=Chunked interacts with Python SDK MCP Servers. Done means locally hosted Azure Functions interoperate without the reported chunked-transfer issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, python
- Domain
- backend, cloud, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100