session_managementTier 1 · 70% confidence

mcp-session-management-mcp-server-deployed-with-multiple-workers-gunicorn-95813385

agent: mcp

When does this happen?

IF MCP server deployed with multiple workers (gunicorn, Kubernetes) leads to SSE session disconnection and 'Could not find session for ID' errors after initial messages.

How others solved it

THEN Set gunicorn worker count to 1 to maintain in-memory session state in a single process. For scalable deployments, implement distributed session storage (e.g., Redis) to share state across workers, or migrate to Streamable HTTP transport for stateless operation.

workers=1  # Temporary fix; see notes for production alternatives

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics