You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
filesystem in the directory mounted with rclone does not work #531
Severity 2: On current v2/main, the 'Parent directory does not exist' error is raised when Node's realpath reports ENOENT for the target and for the allowed root; whether realpath still fails on rclone (WinFsp) drives on Windows cannot be confirmed without a Windows rclone repro, and the reporter's two-line report gives no version or configuration.
Urgency 1: no time pressure
Bonuses: +1 bug label
Could not be confirmed or ruled out on v2 (checked by reading the current code); kept open for a maintainer.
Board: Servers V2 (#43), Status Incoming, awaiting maintainer review (no milestone yet). Part of the backlog triage in #4875.
We could not reproduce this, and the path-validation code has been rewritten several times since this report (v0.6). On the current release, "Parent directory does not exist" means Node's fs.realpath reported the drive path itself as missing.
With rclone/WinFsp mounts, a common cause is that the drive letter exists only in the logon session that created it. If the MCP client starts the server elevated, as a service, or in another session, Z: does not exist for that process.
Closing as cannot reproduce. If it still happens with the latest @modelcontextprotocol/server-filesystem, please open a new issue with:
the exact rclone mount command
the client config (the args passed to the server)
the output of node -e "require('fs').promises.realpath('Z:\\').then(console.log, console.error)" run in the same context as the client
Activity
DoiiarX commentedon Jan 16, 2025
It shows
Error:
Error: Parent directory does not exist: Z:\N100
cliffhall commentedon Oct 19, 2026
Triage: Priority Low (total 4)
buglabelCould not be confirmed or ruled out on v2 (checked by reading the current code); kept open for a maintainer.
Board: Servers V2 (#43), Status
Incoming, awaiting maintainer review (no milestone yet). Part of the backlog triage in #4875.cliffhall commentedon Oct 29, 2026
We could not reproduce this, and the path-validation code has been rewritten several times since this report (v0.6). On the current release, "Parent directory does not exist" means Node's
fs.realpathreported the drive path itself as missing.With rclone/WinFsp mounts, a common cause is that the drive letter exists only in the logon session that created it. If the MCP client starts the server elevated, as a service, or in another session,
Z:does not exist for that process.Closing as cannot reproduce. If it still happens with the latest
@modelcontextprotocol/server-filesystem, please open a new issue with:node -e "require('fs').promises.realpath('Z:\\').then(console.log, console.error)"run in the same context as the clientWe'll pick it up from there.