You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+28-28Lines changed: 28 additions & 28 deletions
Original file line number
Diff line number
Diff line change
@@ -214,19 +214,15 @@ For remote servers, set up a Streamable HTTP transport that handles both client
214
214
215
215
#### With Session Management
216
216
217
+
In some cases, servers need to be stateful. This is achieved by [session management](https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#session-management).
res.status(400).send('Invalid or missing session ID');
302
-
return;
303
-
}
304
-
305
-
const transport =transports[sessionId];
306
-
awaittransport.handleRequest(req, res);
307
-
});
302
+
app.delete('/mcp', handleSessionRequest);
308
303
309
304
app.listen(3000);
310
305
```
@@ -698,7 +693,7 @@ This setup allows you to:
698
693
699
694
### Backwards Compatibility
700
695
701
-
The SDK provides support for backwards compatibility between different protocol versions:
696
+
Clients and servers with StreamableHttp tranport can maintain [backwards compatibility](https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#backwards-compatibility) with the deprecated HTTP+SSE transport (from protocol version 2024-11-05) as follows
702
697
703
698
#### Client-Side Compatibility
704
699
@@ -708,21 +703,26 @@ For clients that need to work with both Streamable HTTP and older SSE servers:
0 commit comments