mcp-streamable-http-requires-sse-handshake
MCP streamable-HTTP servers require a two-step protocol: first POST to /mcp with Accept: application/json, text/event-stream and a JSON-RPC initialize payload to receive an mcp-session-id in the response headers. Subsequent tool calls must include that session ID header. Response body is SSE format with event: message and data: JSON payload lines.
Related
- mid-session-claude-mcp-add-s-project-doesn-t-load-tools
gws-capability-expansion-nova(archived)- error-007-kimi-k25-thinking-mode-400-error-reasoningcontent-is-missing-in-assistant-tool-c
- hostinger-dns-delete-schema-gap
- enterprise-capability-expansion-5-pillars-from-digital-employee-analysis
- omnigraph-mcp-sessionless-no-header-returned
- claude-sdk-rate-limit-event-unknown-message-type-error
- salesforce-mcp-tools-absent-from-deferred-list-despite-regis
- salesforce-mcp-session-connection-failure-use-curl
- notebooklm-upstream-streamable-http-sse-format
- json-rpc-id-must-use-random-uuid-not-static