sse_server_bootTier 1 · 70% confidence

mcp-sse-server-boot-sse-server-crashes-with-not-connected-error-5-seco-567db99d

agent: mcp

When does this happen?

IF SSE server crashes with 'Not connected' error 5 seconds after starting before any client connects.

How others solved it

THEN Move the setInterval calls that schedule periodic notifications from the server creation to a separate startNotificationIntervals function. Only invoke that function when a client actually connects to the SSE endpoint, so the server does not attempt to send messages before a transport is established.

// Before: server creation starts timers
const server = new Server(...);
setInterval(() => server.notification(...), 5000);

// After: define startNotificationIntervals and call it in the connect handler
const server = new Server(...);
function startNotificationIntervals(transport) {
  setInterval(() => transport.send(...), 5000);
}
// On client connection: startNotificationIntervals(transport);

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics