A secure Model Context Protocol (MCP) server for executing commands in Windows Subsystem for Linux (WSL) with built-in safety features and validation
Most developer tooling work still happens through a UI a human drives. MCP Wsl Exec MCP server moves it into the conversation instead. A secure Model Context Protocol (MCP) server for executing commands in Windows Subsystem for Linux (WSL) with built-in safety features and validation.
A Model Context Protocol (MCP) server for Windows + Claude Desktop users to interact with Windows Subsystem for Linux (WSL). Provides both read-only information gathering and secure command execution capabilities.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The server publishes 9 tools. What each one is for:
get_system_info — The get_system_info tool exposed by this serverget_directory_info — The get_directory_info tool exposed by this serverget_disk_usage — The get_disk_usage tool exposed by this serverget_environment — The get_environment tool exposed by this serverlist_processes — The list_processes tool exposed by this serverexecute_command — The execute_command tool exposed by this serverconfirm_command — Confirm execution of a dangerous command that was flagged by safety checksSetup — The Setup tool exposed by this serverPublishing — The project uses changesets for version management. To publish:Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Wsl Exec's toolset — get_system_info, get_directory_info, get_disk_usage and 6 more — is a fair guide to whether it matches your workflow. It is maintained by spences10; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Wsl Exec's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| get_system_info | The get_system_info tool exposed by this server. |
| get_directory_info | The get_directory_info tool exposed by this server. |
| get_disk_usage | The get_disk_usage tool exposed by this server. |
| get_environment | The get_environment tool exposed by this server. |
| list_processes | The list_processes tool exposed by this server. |
| execute_command | The execute_command tool exposed by this server. |
| confirm_command | Confirm execution of a dangerous command that was flagged by safety checks. |
| Setup | The Setup tool exposed by this server. |
| Publishing | The project uses changesets for version management. To publish: |
{
"mcpServers": {
"mcp-wsl-exec": {
"command": "npx",
"args": ["-y", "mcp-wsl-exec"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.