Back to Signal Feed
CodeTracked since May 19, 2026

Add 800-second timeout to Superset MCP streaming routes

The MCP stream endpoints `/api/agent/mcp` and `/api/v2/agent/mcp` now set `maxDuration = 800` explicitly, replacing the implicit Vercel default timeout that previously killed sessions at 300 seconds.

VercelmaxDurationMCP/api/agent/mcp

What Happened

  • The MCP stream endpoints `/api/agent/mcp` and `/api/v2/agent/mcp` now set `maxDuration = 800` explicitly, replacing the implicit Vercel default timeout that previously killed sessions at 300 seconds.
  • The MCP stream endpoints `/api/agent/mcp` and `/api/v2/agent/mcp` now set `maxDuration = 800` explicitly, replacing the implicit Vercel default timeout that previously killed sessions at 300 seconds.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

This change introduces an explicit `export const maxDuration = 800` in `apps/api/src/app/api/agent/[transport]/route.ts` and `apps/api/src/app/api/v2/agent/[transport]/route.ts`, extending MCP session lifetime from Vercel’s 5-minute fallback to about 13 minutes on those SSE/streaming routes.

Why Track This

Why It Matters

Users running Cursor MCP sessions against Superset should see fewer abrupt session terminations, so long AI coding sessions are less likely to be cut off mid-task; operators should now monitor for sessions still ending near the new 800-second limit and verify that longer-running sessions do not increase function recycle pressure or retry storms.

Impact

Users running Cursor MCP sessions against Superset should see fewer abrupt session terminations, so long AI coding sessions are less likely to be cut off mid-task; operators should now monitor for sessions still ending near the new 800-second limit and verify that longer-running sessions do not increase function recycle pressure or retry storms.

What To Watch Next

  • Watch whether Vercel becomes a repeated pattern.
  • Track follow-up changes around Model Context Protocol.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: monitor_sessions_reaching_800s_limit, watch_cursor_client_behavior_after_timeout_change.
Open Topic TimelineOpen Technical EventOpen Original Sourcemonitor_sessions_reaching_800s_limit / watch_cursor_client_behavior_after_timeout_change / track_vercel_timeout_error_rate_trend

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

superset-sh/superset PR #4709: fix(api): add maxDuration=800 to MCP agent routes to prevent 300s timeout

Issue: Vercel’s default 300s function timeout was terminating MCP sessions and causing `Task timed out after 300 seconds`; fix: set both MCP stream route files to `maxDuration = 800`.