WSL Manager MCP
A WSL distro manager with a GUI and an MCP server so an agent can manage distros and run commands inside them
- 4,059 ★ on the repository
- Last commit
Broad access
Why this level
- MCP tools run commands inside distros and VMs
- It can connect to distros over SSH
Install
- Works in
Manual install
claude mcp add wsl-manager -- npx -y mcp-remote http://127.0.0.1:59133/mcpFirst enable the MCP server in the app settings (Pro) and supply the token shown there.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- MCP tools run commands inside distros and VMs
- It can connect to distros over SSH
This is third-party code. Review the repository files before installing.
What it does
WSL Manager gives a GUI for the Windows Subsystem for Linux and native VMs on macOS: install, back up, move and configure distros without console flags. A built-in MCP server exposes the same tools as the internal chat: list and inspect distros, run commands, edit config, create snippets, mount disks and reach WSL over SSH. It also offers a read-only mode for clusters: inspect workloads, pods, events and logs without making changes.
Who it is for. For developers on Windows and macOS who manage WSL distros or local VMs and want to do it through an agent.
Good fit when
- You want an agent to list your distros and run a command inside a chosen one
- You want to manage WSL from Claude Desktop, Claude Code or another MCP client
- You need SSH access to WSL from an assistant
Not a fit when
- You do not use WSL or local VMs
- You cannot give an agent the right to run commands in your distros
Example request
Show me which WSL distros I have and run a package update inside UbuntuMCP
- Transport
- http
- Authentication
- API key
Limitations
The MCP server is enabled in settings and belongs to the paid Pro tier. It listens only on the loopback address 127.0.0.1:59133/mcp and is guarded by a token. For stdio clients the HTTP endpoint is bridged via mcp-remote. MCP tools can run commands inside distros, so access must be restricted.
How to disable. Turn off the MCP server in the app settings, remove the server from your MCP client config and uninstall the app if needed.
FAQ
Is the MCP server reachable from the network?
No. It listens only on the 127.0.0.1 loopback and requires the token shown in settings.
Can the agent only read cluster state?
Yes, clusters have a read-only mode: workloads, pods, events and logs, with no right to restart anything.
Discussion
No questions or reviews yet.
Related
MCP serversA local agent runtime and MCP gateway with 298 tools: files, Git, processes, Chrome browser, Windows and Office
Console Automation MCP gives an agent local shells and SSH sessions: input, output, error detection, long processes
The remote MCP server of Devopness, a platform that builds infrastructure and deploys apps in your own cloud accounts
MCP server giving an agent a PowerShell 7 console shared with the user: commands appear live, passwords and MFA codes stay manual.
CLI and app for workspaces: each AI agent gets its own container from a shared devcontainer.json, with an MCP server and a skill
Azure DevOps MCP server
Azure DevOps MCP Server
Official Microsoft MCP server for Azure DevOps: work items, repositories, builds, test plans, and wiki from the agent
README in short
The README describes WSL Manager as a GUI manager for WSL distros, and on macOS also native VMs. It covers install, backup, move and config without flags, a built-in AI chat with tools and an MCP server that exposes the same tools to external clients. It shows enabling MCP on the Pro tier, the loopback address with a token, the mcp-remote bridge for stdio clients and config examples for Claude Desktop, Claude Code and opencode.