Windows and WSL are close neighbors with different path conventions and execution environments. wslgate provides a bridge for workflows that need to cross that boundary, combining a command-line interface with MCP tools for compatible clients.
Make the destination clear
Path translation, distribution discovery, and optional distribution selection help make a command or file operation explicit. A path on Windows is not automatically meaningful inside every WSL distribution, so resolving the environment is part of doing the work correctly.
Handle files as files
File read and write operations use encoding and quoting strategies designed for crossing the process boundary. Keeping file data separate from command construction reduces the temptation to build fragile shell strings for routine transfers. Execution remains a separate capability with its own consequences.
Choose the access you need
Read-only mode disables command execution and file writes. That provides a narrower configuration for inspection-oriented clients. A writable bridge can change files and run commands in the selected environment, so configure it for the tasks you intend to allow. The repository documents setup, path handling, and available tools.
Explore wslgate → · Source and documentation ↗