feat(cortex): serve /mcp in stateless JSON mode (broad client compat)#103
Open
ApiliumDevTeam wants to merge 1 commit into
Open
feat(cortex): serve /mcp in stateless JSON mode (broad client compat)#103ApiliumDevTeam wants to merge 1 commit into
ApiliumDevTeam wants to merge 1 commit into
Conversation
aingle's MCP tools are all request/response (no server-initiated notifications), so the SSE notification stream isn't needed. Stateful streamable-HTTP mode requires clients to open a GET text/event-stream channel, which some HTTP MCP clients don't, yielding 406 Not Acceptable. Stateless + json_response = plain JSON request/response, spec-compliant (MCP 2025-06-18) and compatible with more clients.
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.
Summary
Switches the
/mcpStreamable HTTP endpoint to stateless +json_responsemode.aingle's 25 MCP tools are all request/response (no server-initiated notifications), so the SSE notification stream isn't needed. In the default stateful mode, rmcp requires clients to open a
GET /mcptext/event-streamchannel; some HTTP MCP clients (e.g. Claude Code's local HTTP transport) don't, producing406 Not Acceptable: Client must accept text/event-stream. Stateless +json_responsereturns plain JSON request/response (spec-compliant, MCP 2025-06-18) and works with more clients.Change
StreamableHttpServerConfig::default().with_allowed_hosts(..).with_stateful_mode(false).with_json_response(true)(one config line).Verification
/mcpover HTTP returned406 ... must accept text/event-stream(stateful GET channel). After the change, Claude Code connects and drives the full tool flow (create_triple → query → signed dag_history) over HTTP.POST /mcp→200,Content-Type: application/json, noMcp-Session-Id(stateless);GET /mcp→405(no SSE channel).