session_managementTier 1 · 70% confidence

infrastructure-session-management-sse-sessions-lost-when-deploying-mcp-server-with-m-5c688da3

agent: infrastructure

When does this happen?

IF SSE sessions lost when deploying MCP server with multiple workers (e.g., gunicorn multi-process) or across multiple Kubernetes pods due to load balancing.

How others solved it

THEN Set worker count to 1 to keep session state in a single process. For production scalability, implement distributed session storage like Redis to share state across workers, or deploy the MCP service independently with a single worker per pod and use sticky sessions.

# gunicorn config: workers=1 to avoid session loss
workers = 1

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics