Kyle-Undefined/gandr
A WSL bridge for Claude Desktop on Windows that routes MCP tool calls into Claude Code running inside Linux.
Platform-specific configuration:
{
"mcpServers": {
"gandr": {
"command": "npx",
"args": [
"-y",
"gandr"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
> Note: This project exists as a workaround until Claude Code natively supports WSL/Windows integration with Claude Desktop. Tracked in anthropics/claude-code#12506.
Gandr is a WSL bridge for Claude Desktop on Windows.
It works as an MCP server, not a native Claude Desktop integration. Claude Desktop communicates with Gandr through the Model Context Protocol over stdio, and Gandr exposes a set of tools; one that delegates tasks to Claude Code running inside WSL, and several that operate on the WSL filesystem directly.
When Gandr delegates a task, it spawns Claude Code in non-interactive print mode (claude -p), writes the prompt over stdin, and streams the result back to Claude Desktop.
This is not Claude Desktop running natively in WSL. It is Claude Desktop on Windows making MCP tool calls that get routed into WSL through Gandr.
The Claude Desktop Code tab attempts to run Claude Code natively on Windows and does not route through Gandr or WSL. It will not work with this setup. Use the chat tab for all tasks.
Gandr is for people who want Claude Desktop's chat UI, but want execution to happen inside a real Linux environment instead of the Windows host.
It keeps Claude Desktop as the front end while routing coding, shell, and file tasks through Claude Code running in WSL. That means Claude works with the same Linux tools, dotfiles, auth state, and hooks you already use in your normal WSL setup.
The name comes from Old Norse _gandr_, a magical conduit or channel. It shares its word roots with Galdur.
claude available on your WSL PATHLoading reviews...