claude-code - 💡(How to fix) Fix Macos MCP connector crashes after ~17h despite system sleep being prevented

Summary

The built-in Macos MCP connector (installed via Preferences → Connectors) exits unexpectedly after extended uptime. The Mac does not sleep — system sleep is actively prevented by Claude itself — so this is not a wake-from-sleep issue.

Environment

• macOS: 26.4.1 (Build 25E253, arm64)
• Claude Desktop: 1.7196.0
• MCP connector: Macos (built-in, installed via Preferences → Connectors)

Observed behavior

Server started cleanly at session boot, tools listed successfully. After ~17 hours of uptime with no activity on the Macos MCP tools, the process exited:

2026-05-18T00:56:00.048Z [Macos] [info] Server transport closed
2026-05-18T00:56:00.081Z [Macos] [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.
2026-05-18T00:56:00.095Z [Macos] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation

Power management state at time of crash

System sleep was not a factor — Claude was actively preventing it:

sleep                0 (sleep prevented by coreaudiod, sharingd, Claude, powerd, Claude)
displaysleep         5
hibernatemode        3
standby              1

Expected behavior

Connector process should remain alive for the duration of the Claude session, or auto-restart on exit.

Notes

• The connector does reconnect on next session start — no user action required
• No stderr output was produced by the Macos MCP process at crash time (based on log content)
• The crash appears to be an idle-timeout or uncaught exception in the connector process itself