MCP Architecture

Run ticketdesk as three replicas behind an ordinary round-robin load balancer and connect a client that speaks revision 2025-11-25 over HTTP. The client's initialize request lands on replica A, which creates a session and returns its identifier in an Mcp-Session-Id header. The next request carries that header and lands on replica B, which has never heard of the session. We recorded the answer from the official Python SDK on 27 September 2026: