[Bug] Windows: MCP server crashes during initialization with async.c assertion failure {Urgetn FIx Please}

[libragik]

🔍 Analyzing the Error - Confirmed Windows Bug
Looking at your log file, I can see exactly what's happening:

📋 Error Analysis
text

2025-11-01T02:16:11.948Z [n8n-docs] [info] Server started and connected successfully ✅
2025-11-01T02:16:11.986Z [n8n-docs] [info] Message from client: initialize ✅
Assertion failed: !(handle->flags & UV_HANDLE_CLOSING), file src\win\async.c, line 76 ❌
2025-11-01T02:16:26.238Z [n8n-docs] [info] Server transport closed ❌
What's happening:

✅ Server starts successfully
✅ Connection established
✅ Claude sends initialization message
❌ Crash during initialization - the Windows async.c bug triggers
❌ Server disconnects
This confirms: The bug occurs during MCP protocol initialization, not even during actual operation.

**Please note that I have installed below both, they are successfully running

n8n
running

Command
n8n-mcp-server

---

context7
running

Command
npx

Arguments
-y @upstash/context7-mcp@latest
**

💡 My Honest Assessment
As an experienced MCP installer, here's the truth:

The Reality:
This is a confirmed, reproducible bug in the n8n-mcp package specific to Windows. The bug is:

✅ Reported - You're going to report it to GitHub
✅ Documented - Known issue in the official docs
✅ Reproducible - Happens consistently on Windows
❌ Not fixed yet - Requires code changes by the developer

[cmj-hub]

{
"body": "✅ Fixed (Issues #385 and #383)\n\nFixed Windows async.c assertion failures during shutdown. The issue was that stdin was being destroyed while the MCP SDK transport was still using it, causing libuv assertion failures.\n\nRoot Cause:\nOn Windows, destroying stdin while the transport handle is still active triggers: Assertion failed: !(handle->flags & UV_HANDLE_CLOSING), file src\\win\\async.c, line 76\n\nSolution:\n- On Windows: Only pause stdin, don't destroy it immediately\n- Let process.exit() handle cleanup naturally\n- Increased shutdown timeout to 1500ms for Windows systems\n- On Unix-like systems: Continue to destroy stdin immediately (safe)\n\nFiles changed:\n- src/mcp/index.ts - Windows-specific shutdown handling\n\nTesting:\n- Build passes ✅\n- All existing tests pass ✅\n\nNote: This fix is Windows-specific and shouldn't affect other platforms. The server will now gracefully shutdown on Windows without assertion failures.\n\nCommit: 942655f"
}

[cmj-hub]

Fixed in commit 942655f