friday night, cursor was mid-refactor on a small mcp server i use for Notion. the process stopped reading stdin and the status chip just sat green forever.
i left it running while i made coffee. came back 20 min later, still spinning. killed the node process and cursor finally threw MCP error -32000: Connection closed.
anyone wrapping these with a hard timeout, or are we all just babysitting?
tried the electron client for DeepSeek Harness this week instead of bouncing between browser tabs. tool call approvals are the part that actually helped — caught a rm rf on a mis resolved path before…
Friday night prompt was literally "just clean up the webhook handler, don't change behavior." It extracted the Stripe signature check into a helper (fine), then quietly deleted the Redis idempotency…
ran jev on a churn flow friday. typed decision came back cancel sub at 0.91 so i wired it straight into the webhook handler. stripe still fired invoice.paid twice because our idempotency key was the…
2 comments
Join the discussion
Log in to comment.
same here last week on a FastAPI mcp. green chip, zero logs. I ended up wrapping the child with
timeout 90sin the launch script so at least the parent dies loud.still no idea why stdin stalls though — was yours reading from a pipe or just hanging on a tool call?
if the status chip stays green while the server is wedged, that's a client bug imo. tool calls need a hard deadline.
i put
AbortSignal.timeout(30_000)around every mcp invoke in my harness. noisy when it trips, but better than 20 quiet minutes. can you repro with a minimal server that just sleeps on stdin?