servers / mcp-wsl-exec

mcp-wsl-exec

communitystdiolocalwrite capablehealthy

01Tools · 7

How to read this: tool names here are observed from a live tools/list handshake. The Risk label is a heuristic inferred from the tool name (write/destructive verbs), not from executing the tool — a conservative guess, not a verified capability. We never escalate risk from a description. Found one that's wrong? Tell us — we fix on report.

ToolRiskSide effectsApproval
confirm_command
Confirm dangerous command execution
unknownunknownunknown
get_directory_info
Get directory contents and info
readfalseunknown
get_disk_usage
Get disk space information
readfalseunknown
list_processes
List running processes in WSL
readfalseunknown
get_system_info
Get WSL system information
readfalseunknown
get_environment
Get WSL environment variables
readfalseunknown
execute_command
Execute a command in WSL (use read-only tools when possible)
writetrueunknown

02Install & source
npx -y mcp-wsl-exec
npx

03Access granted
Execute code · write

The access this server can exercise, inferred from its verified tools — not a declared OAuth scope.


05Provenance & freshness
sourcesGitHub repo search [p4]
last_checked2026-08-16 19:10Z
next_check2026-08-16 22:10Z
cadenceevery 3h
verifiedtools_list:passed handshake:passed metadata:passed tools_list:passed handshake:passed metadata:passed tools_list:passed handshake:passed metadata:passed tools_list:passed
index_statusindex9 unique facts >= 5

06Badge

Add the “as seen on MCPExplorer” badge to your README. mcp-wsl-exec MCP — as seen on mcpexplorer.com

[![mcp-wsl-exec MCP — as seen on mcpexplorer.com](https://mcpexplorer.com/badge/mcp-wsl-exec.svg)](https://mcpexplorer.com/servers/mcp-wsl-exec)

Next step

This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.

Explore loadouts →
mcp-wsl-exec — MCPExplorer