chore: Gracefully fail when the server is down

The server might be closed because the connection made the
server die or because it's a unit test. In that case, do
not fail, just log the error and continue.

This is not a critical feature, in case that we couldn't
sync once, we will try again at some point or just let
it be.

Author: kmruiz

src/resources/resource.ts

@@ -4,6 +4,7 @@ import { UserConfig } from "../common/config.js";
 import { Telemetry } from "../telemetry/telemetry.js";
 import type { SessionEvents } from "../common/session.js";
 import { ReadResourceCallback, ResourceMetadata } from "@modelcontextprotocol/sdk/server/mcp.js";
+import logger, { LogId } from "../common/logger.js";
 
 type PayloadOf<K extends keyof SessionEvents> = SessionEvents[K][0];
 
@@ -58,8 +59,16 @@ export function ReactiveResource<Value, RelevantEvents extends readonly (keyof S
         });
 
         private async triggerUpdate() {
-            await this.server.mcpServer.server.sendResourceUpdated({ uri });
-            this.server.mcpServer.sendResourceListChanged();
+            try {
+                await this.server.mcpServer.server.sendResourceUpdated({ uri });
+                this.server.mcpServer.sendResourceListChanged();
+            } catch (error: unknown) {
+                logger.warning(
+                    LogId.serverClosed,
+                    "Could not send the latest resources to the client.",
+                    error as string
+                );
+            }
         }
 
         reduceApply(eventName: SomeEvent, ...event: PayloadOf<SomeEvent>[]): void {