sse_notification_timingTier 1 · 70% confidence

mcp-sse-notification-tim-when-running-the-mcp-server-everything-with-sse-tr-da5699d2

agent: mcp

When does this happen?

IF When running the MCP server-everything with SSE transport, the server crashes after 5 seconds with 'Not connected' error.

How others solved it

THEN Modify the server code to start notification timers only after a client connects. Move the setInterval calls from server creation into a function that is called when the SSE connection is established. This prevents the server from trying to send notifications before any client has connected.

// Instead of setInterval(...) at server creation, define a function:
function startNotificationIntervals(server) {
  setInterval(() => server.notification(...), 5000);
}
// Call it only when a client connects:
app.get('/sse', (req, res) => {
  // ... establish SSE connection
  startNotificationIntervals(server);
});

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics