wonderwhy-er
Error: MCP error -32001: Request timed out
Mac OS, node v22.14.0 (npm v10.9.2) Logs:
2025-03-23T18:30:58.409Z [desktopCommander] [info] Initializing server...
2025-03-23T18:30:58.412Z [desktopCommander] [info] Server started and connected successfully
2025-03-23T18:30:58.413Z [desktopCommander] [info] Message from client: {"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0}
npx: installed 57 in 12.39s
2025-03-23T18:31:56.632Z [desktopCommander] [info] Message from client: {"jsonrpc":"2.0","method":"notifications/cancelled","params":{"requestId":0,"reason":"Error: MCP error -32001: Request timed out"}}
2025-03-23T18:31:56.633Z [desktopCommander] [info] Client transport closed
2025-03-23T18:31:56.634Z [desktopCommander] [info] Server transport closed
2025-03-23T18:31:56.634Z [desktopCommander] [info] Client transport closed
2025-03-23T18:31:56.635Z [desktopCommander] [info] Server transport closed unexpectedly, this is likely due to the process exiting early. If you are developing this MCP server you can add output to stderr (i.e. console.error('...') in JavaScript, print('...', file=sys.stderr) in python) and it will appear in this log.
2025-03-23T18:31:56.635Z [desktopCommander] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-23T18:31:56.644Z [desktopCommander] [info] Server transport closed
2025-03-23T18:31:56.644Z [desktopCommander] [info] Client transport closed
2025-03-23T18:31:58.633Z [desktopCommander] [info] Message from client: {"jsonrpc":"2.0","method":"notifications/cancelled","params":{"requestId":0,"reason":"Error: MCP error -32001: Request timed out"}}
2025-03-23T18:31:58.633Z [desktopCommander] [info] Client transport closed
2025-03-23T18:31:58.634Z [desktopCommander] [info] Server transport closed
2025-03-23T18:31:58.634Z [desktopCommander] [info] Client transport closed
2025-03-23T18:31:58.634Z [desktopCommander] [info] Server transport closed unexpectedly, this is likely due to the process exiting early. If you are developing this MCP server you can add output to stderr (i.e. console.error('...') in JavaScript, print('...', file=sys.stderr) in python) and it will appear in this log.
2025-03-23T18:31:58.634Z [desktopCommander] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-23T18:31:58.643Z [desktopCommander] [info] Server transport closed
2025-03-23T18:31:58.643Z [desktopCommander] [info] Client transport closed
I think I cleaned it out in previous release. But not sure We just had new release with bunch of fixes. Can you guys try? https://github.com/wonderwhy-er/DesktopCommanderMCP/releases/tag/v0.1.25
It is published to NPM so smithery install is good
I'll try it out. fwiw, this issue was super intermittent, and it seems to occur for other mcp servers as well -- i suspect its just a "the mcp server hasn't responded to me in time" from claude desktop, but it also doesn't seem to be recoverable, which is weird, but probably on Claude Desktop's end.
Also, gotta say, so glad I stumbled upon this mcp on youtube shorts. probably the only good thing I've gained from doomscrolling, haha.