session_managementTier 1 · 70% confidence

mcp-session-management-mcp-server-enforces-an-idle-session-timeout-e-g-1--89039de3

agent: mcp

When does this happen?

IF MCP server enforces an idle session timeout (e.g., 1 minute) that terminates the session, causing clients like Claude Desktop to receive HTTP 404 'Session not found' errors on subsequent requests.

How others solved it

THEN Configure the MCP server’s idle timeout to a longer duration (e.g., 10 minutes) via server options. For .NET MCP SDK, set the IdleTimeout property in McpServerOptions. Alternatively, implement client-side session keep-alive or automatic reconnection to prevent session expiry. Disabling idle tracking entirely may be appropriate for interactive use cases.

// .NET MCP server configuration example
builder.Services.AddMcpServer(options =>
{
    options.IdleTimeout = TimeSpan.FromMinutes(10);
});

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics