Follow-up to #37. That issue was resolved for the original reporter via the --log-folder workaround, but a newer, more heavily sandboxed Claude environment ("Claude Sciences") blocks Unix socket connections entirely, so the workaround no longer helps. Opening this as a separate tracking issue for that environment.
Description
In a sandboxed Claude environment ("Claude Sciences"), the MATLAB MCP Core Server fails to start when spawned as a child process. As in #37, the server exits during startup with:
Failed to connect to watchdog socket
error: "access denied for socket file"
The difference from #37 is that the sandbox appears to block all Unix socket connection requests, not just socket files in the default temp directory. As a result, the previously recommended workaround does not resolve the problem.
Workaround from #37 does not work here
The --log-folder workaround (relocating the watchdog socket to a user-writable directory) resolved #37 for the original reporter. In this sandboxed environment it does not help, because the socket connection itself is blocked regardless of where the .sock file lives.
Requested fix
Add a supported way to run the server without the watchdog socket, for use in restricted environments where Unix sockets are unavailable. For example a --no-watchdog / --disable-watchdog flag (and/or an equivalent environment variable), so the server can start
even when watchdog IPC cannot be established.
Description
In a sandboxed Claude environment ("Claude Sciences"), the MATLAB MCP Core Server fails to start when spawned as a child process. As in #37, the server exits during startup with:
The difference from #37 is that the sandbox appears to block all Unix socket connection requests, not just socket files in the default temp directory. As a result, the previously recommended workaround does not resolve the problem.
Workaround from #37 does not work here
The
--log-folderworkaround (relocating the watchdog socket to a user-writable directory) resolved #37 for the original reporter. In this sandboxed environment it does not help, because the socket connection itself is blocked regardless of where the.sockfile lives.Requested fix
Add a supported way to run the server without the watchdog socket, for use in restricted environments where Unix sockets are unavailable. For example a
--no-watchdog/--disable-watchdogflag (and/or an equivalent environment variable), so the server can starteven when watchdog IPC cannot be established.