brightspace-mcp-server 3.10.8 → 3.10.9

package/build/index.js

@@ -9,6 +9,7 @@
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 import { enableStdoutGuard, log } from "./utils/logger.js";
+import { guardServerProcess } from "./utils/process-guard.js";
 import { loadConfig } from "./utils/config.js";
 import { TokenManager, AuthRunner } from "./auth/index.js";
 import { D2LApiClient } from "./api/index.js";
@@ -45,10 +46,9 @@ else {
     // ── MCP Server (default) ────────────────────────────────────────────
     // CRITICAL: Enable stdout guard IMMEDIATELY to prevent corruption of stdio transport
     enableStdoutGuard();
-    // Unhandled rejection handler
-    process.on('unhandledRejection', (reason) => {
-        log('ERROR', 'Unhandled promise rejection', reason);
-    });
+    // A stray exception or a closed pipe must not silently drop the client's
+    // transport; see guardServerProcess.
+    guardServerProcess();
     async function main() {
         try {
             // Load configuration

package/build/utils/process-guard.js

@@ -0,0 +1,47 @@
+/**
+ * Purdue Brightspace MCP Server
+ * Copyright (c) 2026 Rohan Muppa. All rights reserved.
+ * Licensed under MIT — see LICENSE file for details.
+ */
+import { log } from "./logger.js";
+const RECONNECT_HINT = "Restart or reconnect the Brightspace MCP server in your MCP client to continue " +
+    "(for example, toggle it off and on in the client's MCP settings, or restart the client).";
+/**
+ * Keep one bad moment from silently killing a stdio MCP server.
+ *
+ * Each MCP client launches its own server process. When that process dies,
+ * the client only ever reports "Transport closed" for every later call, even
+ * calls that never touch the network, while another client's process carries
+ * on fine. Node's defaults are what kill it: an exception thrown from any
+ * event listener, or an EPIPE on stdout with no 'error' listener, ends the
+ * process with nothing useful in the client's log.
+ *
+ * So: a stray exception is logged and the server keeps serving; a stdout pipe
+ * the client has already closed ends the process cleanly, since there is no
+ * one left to answer; and every other way the process stops says why on
+ * stderr, which MCP clients keep as the server's log.
+ */
+export function guardServerProcess(proc = process) {
+    proc.on("uncaughtException", (error) => {
+        log("ERROR", "Uncaught exception; the server is still running", error);
+    });
+    proc.on("unhandledRejection", (reason) => {
+        log("ERROR", "Unhandled promise rejection", reason);
+    });
+    proc.stdout.on("error", (error) => {
+        if (error.code === "EPIPE") {
+            log("INFO", "The MCP client closed the connection (stdout pipe closed); shutting down");
+            proc.exit(0);
+            return;
+        }
+        log("ERROR", "Writing to the MCP client failed", error);
+    });
+    proc.stdin.on("end", () => {
+        log("INFO", "The MCP client closed stdin; the server will stop");
+    });
+    proc.on("exit", (code) => {
+        if (code === 0)
+            return;
+        log("ERROR", `Brightspace MCP server exited with code ${code}. ${RECONNECT_HINT}`);
+    });
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "brightspace-mcp-server",
-  "version": "3.10.8",
+  "version": "3.10.9",
   "mcpName": "io.github.RohanMuppa/brightspace",
   "description": "MCP server for Brightspace (D2L). Check grades, due dates, assignments, announcements, syllabus, rosters and more via Claude, ChatGPT, Cursor, Windsurf, or any MCP client.",
   "type": "module",