Skip to content

fix(cortex): serve /mcp in stateless JSON mode (broad client compat)#109

Merged
ApiliumDevTeam merged 1 commit into
mainfrom
fix/mcp-stateless-cherry
Jul 9, 2026
Merged

fix(cortex): serve /mcp in stateless JSON mode (broad client compat)#109
ApiliumDevTeam merged 1 commit into
mainfrom
fix/mcp-stateless-cherry

Conversation

@ApiliumDevTeam

Copy link
Copy Markdown
Contributor

Cherry-pick of 1c24584 onto current main (the original branch had diverged). Enables stateless + json_response on the MCP HTTP server so clients that don't open a GET text/event-stream channel work without 406/422. 8-line config change; cargo check -p aingle_cortex is clean. Likely fixes the 422 seen when connecting Claude Code to Akashi's MCP.

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.
@ApiliumDevTeam ApiliumDevTeam merged commit 237fe9a into main Jul 9, 2026
13 of 14 checks passed
@ApiliumDevTeam ApiliumDevTeam deleted the fix/mcp-stateless-cherry branch July 9, 2026 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant