modelcontextprotocol / modelcontextprotocol/servers
Unable to start the MCP File System in Windows
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
Description
Filesystem Failed Error
I've tried 2 ways and none of them worked out. I'd appreciate any help:
I belive I have installed all I need:
And no, writing together my username doesn't fix the issue:
mcp.log:
2025-04-17T04:45:39.311Z [info] [filesystem] Initializing server...
2025-04-17T04:45:39.332Z [info] [filesystem] Server started and connected successfully
2025-04-17T04:45:39.334Z [info] [filesystem] Message from client: {"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0}
2025-04-17T04:45:42.401Z [info] [filesystem] Server transport closed
2025-04-17T04:45:42.401Z [info] [filesystem] Client transport closed
2025-04-17T04:45:42.401Z [info] [filesystem] 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-04-17T04:45:42.401Z [error] [filesystem] Server disconnected. For troubleshooting guidance, please visit our debugging documentation
2025-04-17T04:45:42.402Z [info] [filesystem] Client transport closed
2025-04-17T04:48:30.039Z [info] [filesystem] Initializing server...
2025-04-17T04:48:30.053Z [info] [filesystem] Server started and connected successfully
2025-04-17T04:48:30.154Z [info] [filesystem] Message from client: {"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0}
2025-04-17T04:48:30.990Z [info] [filesystem] Server transport closed
2025-04-17T04:48:30.990Z [info] [filesystem] Client transport closed
2025-04-17T04:48:30.990Z [info] [filesystem] 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-04-17T04:48:30.990Z [error] [filesystem] Server disconnected. For troubleshooting guidance, please visit our debugging documentation
2025-04-17T04:48:30.990Z [info] [filesystem] Client transport closed
mcp-server-filesystem.log
2025-04-17T04:45:39.310Z [filesystem] [info] Initializing server...
2025-04-17T04:45:39.331Z [filesystem] [info] Server started and connected successfully
2025-04-17T04:45:39.334Z [filesystem] [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}
Error accessing directory C:\Users\MysticKarax\Desktop: Error: ENOENT: no such file or directory, stat 'C:\Users\MysticKarax\Desktop'
at async Object.stat (node:internal/fs/promises:1032:18)
at async file:///C:/Users/Mystic%20Karax/AppData/Local/npm-cache/_npx/a3241bba59c344f5/node_modules/@modelcontextprotocol/server-filesystem/dist/index.js:33:23
at async Promise.all (index 0)
at async file:///C:/Users/Mystic%20Karax/AppData/Local/npm-cache/_npx/a3241bba59c344f5/node_modules/@modelcontextprotocol/server-filesystem/dist/index.js:31:1 {
errno: -4058,
code: 'ENOENT',
syscall: 'stat',
path: 'C:\Users\MysticKarax\Desktop'
}
2025-04-17T04:45:42.401Z [filesystem] [info] Server transport closed
2025-04-17T04:45:42.401Z [filesystem] [info] Client transport closed
2025-04-17T04:45:42.401Z [filesystem] [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-04-17T04:45:42.401Z [filesystem] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-04-17T04:45:42.402Z [filesystem] [info] Client transport closed
2025-04-17T04:48:30.039Z [filesystem] [info] Initializing server...
2025-04-17T04:48:30.053Z [filesystem] [info] Server started and connected successfully
2025-04-17T04:48:30.154Z [filesystem] [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}
Error accessing directory C:\Users\MysticKarax\Desktop: Error: ENOENT: no such file or directory, stat 'C:\Users\MysticKarax\Desktop'
at async Object.stat (node:internal/fs/promises:1032:18)
at async file:///C:/Users/Mystic%20Karax/AppData/Local/npm-cache/_npx/a3241bba59c344f5/node_modules/@modelcontextprotocol/server-filesystem/dist/index.js:33:23
at async Promise.all (index 0)
at async file:///C:/Users/Mystic%20Karax/AppData/Local/npm-cache/_npx/a3241bba59c344f5/node_modules/@modelcontextprotocol/server-filesystem/dist/index.js:31:1 {
errno: -4058,
code: 'ENOENT',
syscall: 'stat',
path: 'C:\Users\MysticKarax\Desktop'
}
2025-04-17T04:48:30.989Z [filesystem] [info] Server transport closed
2025-04-17T04:48:30.990Z [filesystem] [info] Client transport closed
2025-04-17T04:48:30.990Z [filesystem] [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-04-17T04:48:30.990Z [filesystem] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-04-17T04:48:30.990Z [filesystem] [info] Client transport closed
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the mcp-server-filesystem.log entry for @modelcontextprotocol/server-filesystem/dist/index.js and the ENOENT path C:\Users\MysticKarax\Desktop. Reproduce the Windows configuration with that path and compare it with an existing directory. Done means the failure is explained and the server's behavior for the configured path is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100