modelcontextprotocol / modelcontextprotocol/servers
Add Streamable HTTP support to all reference servers
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe.
When I first started working with the reference servers, I was frustrated that most of the servers only supported stdio transport. If the reference servers are intended to also act as a reference for people looking to implement their own custom servers, having examples of how to change the transport, especially in the typescript-based servers, would be beneficial.
Describe the solution you'd like
All reference servers have a way to run them with both stdio and sse transport. For the typescript servers, the everything implementation could be used as reference.
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 with the TypeScript reference implementation in src/everything/sse.ts and compare how the other reference servers expose transport options. Determine the complete set of reference servers and the intended distinction between Streamable HTTP and SSE; done means each server can run with both stdio and the requested HTTP-based transport.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100