claude-code - 💡(How to fix) Fix [Bug] Filesystem MCP server crashes on startup with "Server transport closed unexpectedly" [1 participants]

[{"error":"Error: Failed to delete keychain entry: security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.\n at vMq (file:///Users/smartepdworkaccount/.nvm/versions/node/v22.22.1/lib/node_modules/@anthropic-ai/claude-code/cli.js:301:272235)\n at process.processTicksAndRejections (node:internal/process/task_queues:103:5)\n at async BUq (file:///Users/smartepdworkaccount/.nvm/versions/node/v22.22.1/lib/node_modules/@anthropic-ai/claude-code/cli.js:480:889)\n at async eR1 (file:///Users/smartepdworkaccount/.nvm/versions/node/v22.22.1/lib/node_modules/@anthropic-ai/claude-code/cli.js:480:787)\n at async pq8 (file:///Users/smartepdworkaccount/.nvm/versions/node/v22.22.1/lib/node_modules/@anthropic-ai/claude-code/cli.js:2986:2123)\n at async fX6 (file:///Users/smartepdworkaccount/.nvm/versions/node/v22.22.1/lib/node_modules/@anthropic-ai/claude-code/cli.js:3011:5687)\n at async file:///Users/smartepdworkaccount/.nvm/versions/node/v22.22.1/lib/node_modules/@anthropic-ai/claude-code/cli.js:3035:3250","timestamp":"2026-04-16T16:48:42.109Z"},{"error":"RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded\n at Socket.onChildStdout (node:child_process:484:14)\n at Socket.emit (node:events:519:28)\n at addChunk (node:internal/streams/readable:561:12)\n at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n at Readable.push (node:internal/streams/readable:392:5)\n at Pipe.onStreamRead (node:internal/stream_base_commons:189:23)","timestamp":"2026-04-16T16:49:17.741Z"}]

TL;DR

The issue may be resolved by resetting the session and checking the Filesystem server connection.

Guidance

• Investigate the "Server transport closed unexpectedly" error in the MCP logs to determine the cause of the Filesystem server crashing.
• Check the keychain entry deletion error and its relation to the session initialization issue.
• Verify the Node.js version and its compatibility with the Cowork app.
• Review the attached logs for any additional error messages or clues.

Example

No specific code snippet can be provided without further information on the Cowork app's internal workings.

Notes

The issue seems to be related to the Filesystem server connection and session initialization. However, without more information on the Cowork app's architecture and the MCP logs, it's difficult to provide a more specific solution.

Recommendation

Apply a workaround by resetting the session and checking the Filesystem server connection, as this may resolve the issue temporarily until a more permanent fix can be found.