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
{{ message }}
Repository navigation
Commit 591ffa2
Browse filesBrowse the repository at this point in the historyBrowse files
Preserve protocol version on session resumption after crash (#326)
Sessions resumed after a bridge crash lost their negotiated protocol
version: session details showed `Protocol: unknown (stateful)` without
the server name, and all requests on the resumed connection were sent
without the required `MCP-Protocol-Version` header. The SDK skips the
initialize handshake when reconnecting with a preserved
`MCP-Session-Id`, so mcpc now seeds the reconstructed transport with the
version persisted in sessions.json.
- Thread the stored `protocolVersion` through the resume path (bridge
manager → bridge → transport), using the SDK transport option intended
for exactly this case
- Derive the protocol era from the restored version so era-dependent
routing keeps working on resumed connections
- Fall back to persisted `serverInfo` in session details after
resumption
- New e2e test crashes the bridge and asserts the resumed session keeps
its protocol version, server info, and session ID (verified to fail
without the fix)
- Also adds an e2e guard asserting stdio sessions report a real protocol
version (the mcpc ≤ 0.5.0 symptom from
modelcontextprotocol/typescript-sdk#1468)
Fixes#324. Refs #325 (follow-up: capabilities/instructions after
resumption).
https://claude.ai/code/session_011pqNs7aoZWzXjgBUxAsias
---------
Co-authored-by: Claude <[email protected]>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
18
18
- On servers using MCP 2026-07-28, `logging-set-level` returns an error (the protocol removed `logging/setLevel`) and the task commands (`tasks-list`, `tasks-get`, `tasks-result`, `tasks-cancel`, `tools-call --task/--detach`) report that the new tasks extension is not supported yet — they keep working unchanged on 2025-11-25 servers.
19
19
- Updated the MCP TypeScript SDK v2 to `2.0.0-beta.5`, which fixes interoperability with 2026-07-28 servers built on the latest SDK betas (they require the new `Mcp-Method` request header that older clients did not send).
20
20
21
+
### Fixed
22
+
23
+
- Sessions resumed after a bridge restart (e.g. crash recovery) no longer lose their negotiated protocol version: session details showed `Protocol: unknown` and, worse, requests were sent without the required `MCP-Protocol-Version` header. The stored version is now restored on resumption, and the server name is shown again in session details.
24
+
21
25
### Deprecated
22
26
23
27
- The `logging-set-level` command is deprecated and will be removed in a future release: MCP 2026-07-28 removed the underlying `logging/setLevel` request. It keeps working on 2025-11-25 servers during the deprecation window.
0 commit comments