feat(mcp): serve the HTTP transport statelessly - #146
Merged
Conversation
go-sdk v1.7.0 offers MCP revision 2026-07-28 (sessionless, server/discover instead of the initialize handshake) over streamable HTTP only when the handler is stateless. Every tool is a self-contained Redmine API call, so there is no session state worth keeping. GET and DELETE now answer 405 and stream resumption via Last-Event-ID is gone; older clients still negotiate down to 2025-11-25 unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Was
BuildHTTPHandlersetsStreamableHTTPOptions.Stateless = true.Warum
go-sdk v1.7.0 offers MCP revision
2026-07-28(sessionless,server/discoverinstead of theinitializehandshake) over streamable HTTP only when the handler is stateless. Without it the HTTP transport is capped at2025-11-25while the stdio transport already speaks2026-07-28.Every tool is a self-contained Redmine API call, so there is no session state worth keeping.
Auswirkung
GETandDELETEnow answer405Last-Event-IDis gone2025-11-25and keep working unchangedVerified against the built binary:
server/discover+tools/listat2026-07-28return 200, legacyinitializestill answers2025-11-25,GETreturns 405.