Desktop Commander
io.github.wonderwhy-er/desktop-commander
MCP server for terminal commands, file operations, and process management
Install surfaces
How Desktop Commander runs, per the official MCP registry entry.
- npm
@wonderwhy-er/[email protected]
Governed execution
How KLA gates calls to Desktop Commander once it is connected.
A published policy defines which Desktop Commander actions an agent may take and under what conditions. Each call passes through a policy gate at the tool-call boundary. Permitted actions execute, with the policy basis recorded. Flagged actions execute and are sampled for scheduled human review. High-stakes actions pause and route to a named reviewer on the Decision Desk. The call, the policy decision, and any approval are sealed as an evidence record.
KLA also governs the agent frameworks and model providers you already run. See integrations.