Repository navigation
Interested in helping but need more input on what's not done #6
Description
I would like to start (maybe a discussion is the best channel) to get a status on what per the protocol is required and what is not working. You mention WebSockets not working but that's not actually a listed transport on other implementations so it would seem a very important "nice to have", but I would like to get more clarity (without reading the source line by line) on what is missing from base implementation so I could roll up my sleeves and start working on it.
I'd love to figure out a way to get this to complete enough to fully interoperate with TypeScript and Python implementations both as a client/server and host.
Activity
salty-flower commentedon Feb 26, 2025
Hi, thank you for the initiative!
The current implementation covers a generic bidirectional stream. That's works for client-spawning-server case like Claude desktop.
For claiming "websocket support", I'd expect the MCP server itself be a long running service accepting and handling incoming connections. So there should be some session management at least. And if multi-user is considered, then authorization, auditing, user management all comes into play. I haven't really thought about how this would shape the SDK.
And for the feature itself, resource and prompt haven't been implemented yet. Only tools are supported for now.