modelcontextprotocol / modelcontextprotocol/typescript-sdk
`Host` abstraction for multiple client → server connections in one process
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.4k
- Forks
- 2.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 4
Description
Multiplexing has recurred for me a few times now—clients often need to connect to multiple servers simultaneously. Might be worth building something for it into the client SDK.
I think it's not too hard (send all list commands to all servers, then associate the IDs you get back with the server for follow-up gets, reads, calls), it's just annoying boilerplate.
Maybe we build an actual Host abstraction into the SDK, which has multiple Clients?
See also https://github.com/modelcontextprotocol/python-sdk/issues/9.
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 reading the TypeScript client SDK entry points and the related Python SDK issue #9. Define how a Host containing multiple Clients should send list commands and associate returned IDs with their servers for follow-up gets, reads, and calls. Done means the abstraction supports simultaneous client-to-server connections without repeated application boilerplate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100