What it does
deskcommand gives an MCP client access to the local machine through 26 tools. They cover starting and driving terminal processes, reading and writing files, making surgical text edits, moving files, inspecting file metadata and searching file contents. It also includes tools for configuration, usage statistics and recent tool calls.
It suits work where an MCP client needs to operate on files or run commands on the user's own computer. Search runs as a session: start_search walks the tree, skipping node_modules, .git and dist, and returns a session id whose results are paged with get_more_search_results. edit_block replaces an exact text block and refuses ambiguous edits, so a block that occurs more than once needs an explicit expected count. read_process_output returns only output that has not been seen yet.
It can run as a stdio MCP server, configured in an MCP client, or through its CLI or Docker setup. Terminal processes run behind an injectable executor; the default spawns real shell processes and buffers their output. The CLI exits with 0 on success, 1 on an operation error and 2 on a usage error. The project is released under the MIT license.
Limitations and requirements
write_pdf writes the supplied content as-is and has no PDF layout engine. Search executes synchronously in-process rather than streaming from a ripgrep subprocess. The default executor spawns real shell processes on the local machine.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/deskcommand
Run terminal processes, edit files and search code on the local machine from an MCP client.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it