Wonderwhy-er/DesktopCommanderMCP is an MCP server that lets AI clients search and edit files, run terminal commands, and manage computer processes. It is used to give coding agents practical control over a local development environment through chat. The catalogue add-ons extend or configure this server and its agent workflows.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/wonderwhy-er/DesktopCommanderMCPWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/wonderwhy-er/desktopcommandermcp/desktop-commander)<a href="https://agentmods.dev/mcp/wonderwhy-er/desktopcommandermcp/desktop-commander"><img src="https://agentmods.dev/badge/mcp/wonderwhy-er/desktopcommandermcp/desktop-commander/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/wonderwhy-er/desktopcommandermcp/desktop-commander"><img src="https://agentmods.dev/badge/mcp/wonderwhy-er/desktopcommandermcp/desktop-commander.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
desktop-commander scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
4 near-identical copies found in the catalogue:
- desktop-commander — 100% identical, 0 lines differ
- desktop-commander — 91% identical, 5 lines differ
- desktop-commander — 91% identical, 2 lines differ
- desktop-commander — 91% identical, 2 lines differ
What it actually says
{
"desktop-commander": {
"command": "npx",
"args": [
"-y",
"@wonderwhy-er/desktop-commander@latest"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A 3599f78992eb
desktop-commander is an MCP server published in the GitHub repository wonderwhy-er/DesktopCommanderMCP (10,067 stars, last pushed today), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
mcp-terminal-server
MCP server "mcp-terminal-server" as configured in Unfathomable-siren38/mcp-terminal-server. Runs locally from the mcp-terminal-server npm package.
salva
MCP server "salva" as configured in 0xRyanlee/salva. Runs apps.mcp with /Volumes/Astoria/Projects/salva/.venv/bin/python.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.
vscode-automation-mcp
MCP server "vscode-automation-mcp" as configured in microsoft/vscode. Launched with npm --prefix test/mcp run start-stdio.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.