Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

filesystem couldn't use the network mapped driver name, only the unc path in windows 11 23h2 #235

Open
dave2nian opened this issue Dec 5, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@dave2nian
Copy link

Describe the bug
in my windows 11 23h2,

`C:\net use z:
Local name Z:
Remote name \davens\Multimedia
Resource type Disk
Status OK

Opens 2

Connections 1

The command completed successfully.`

claude_decktop_config.json content as below:
{ "mcpServers": { "filesystem": { "command": "npx", "args": [ "-y", "@modelcontextprotocol/server-filesystem", "Z:\\2024-MyProgramFiles" ] } } }

if I used Z: drive in the claude_decktop_config.json, z: or Z: . MCP got "Error: Parent directory does not exist: z:"

if I used the UNC path in the claude_decktop_config.json. MCP agent works well.

{ "mcpServers": { "filesystem": { "command": "npx", "args": ["@modelcontextprotocol/server-filesystem", "\\\\davens\\Multimedia\\2024-MyProgramFiles"] } } }

image

this problem only happen on the mapped network driver. if it is a local driver, it is fin for works.

@dave2nian dave2nian added the bug Something isn't working label Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant