Design SDK changes for stateless & sessionless MCP#919
Design SDK changes for stateless & sessionless MCP#919maciej-kisiel wants to merge 3 commits intomainfrom
Conversation
|
Hi @yarolegovich, @guglielmo-san, @jba, I have a draft of the first part of the design for stateless/sessionless MCP that's coming in the next spec version. It's focused on the connection establishment logic. PTAL if you're interested and let me know if you have any feedback. |
| New types in `protocol.go`: | ||
|
|
||
| ```go | ||
| const ErrCodeUnsupportedProtocolVersion = -32602 // INVALID_PARAMS per SEP-2575 |
There was a problem hiding this comment.
asked for a dedicated code modelcontextprotocol/modelcontextprotocol#2575 (comment)
| `resource/unsubscribe` when `>= 2026-06-30`. | ||
|
|
||
| > [!WARNING] | ||
| > Deprecated APIs: |
There was a problem hiding this comment.
how long are we going to keep them deprecated and will the new subscriptions/listen method fallback to old-protocol version RPCs?
if the answer to the latter is negative, as an MCP client developer I'm kind of incentivised to keep using ClientSession.Subscribe() and ClientSession.Unsubscribe() APIs, because this way I write the same code for old and new servers
There was a problem hiding this comment.
Our only way to remove deprecated APIs is to release v2. But I hear your argument, maybe it's actually better to hold off with making them deprecated until we have designed how the replacement would look like in v2 and backport it to v1. Deprecation without suggested replacement may not be received well.
maciej-kisiel
changed the title
2 participants
No description provided.