Desktop Commander (local) logo

Desktop Commander (local)

Beta

A community server that runs shell commands and edits files anywhere on the developer's Mac. Few local servers reach further.

  • Developer Tools
  • Local
Runs
On the developer's Mac
Launched with
npx, Docker
Platform
macOS
Publisher
Community (wonderwhy-er)

How it works

Every agent request passes through Ferentin policy before it reaches Desktop Commander (local).

It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y @wonderwhy-er/desktop-commander or docker run -i --rm mcp/desktop-commander.

Ferentin's endpoint agent finds Desktop Commander (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.

  1. AI agentAsks for something
  2. Ferentin policies
  3. Desktop Commander (local) MCP serverRuns on the developer's Mac
  4. Governed resultChecked, logged, returned

About Desktop Commander (local)

A community server that runs shell commands and edits files anywhere on the developer's Mac. Few local servers reach further.

Frequently asked about Desktop Commander (local)

How do I connect Desktop Commander (local) to Ferentin?
Enroll your Macs with the Ferentin endpoint agent, then add Desktop Commander (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
Is the Desktop Commander (local) integration generally available?
The Desktop Commander (local) integration is currently beta on Ferentin.