About deskcommand
deskcommand is a local-machine toolkit for command-line users and MCP clients. It combines terminal process control, file operations, and session-based code search, with configuration and usage tools alongside.
Key features
- 01Start and control terminal processes
- 02Read, write, move, and edit files
- 03Search file contents with paginated results
- 04Inspect configuration and recent calls
Use cases
- 01Run and inspect a local terminal process
- 02Make exact text edits to project files
- 03Search a local tree and page through matches
MCP support
The stdio MCP server exposes 26 tools for local processes, filesystem operations, search, configuration, and usage inspection.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
26Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| path | string | Yes | The directory path to create or ensure exists |
Details
From the project READMEdeskcommand
Work on the local machine from the command line or as a stdio MCP server: start and drive terminal processes, read and write files, make surgical text edits, move files, inspect metadata, and search file contents — with configuration, usage and recent-call tools alongside.
Filesystem and search are real local implementations. Search runs
as a session: start_search walks the tree (skipping
node_modules, .git and dist) and returns a session id whose
results paginate with get_more_search_results. edit_block
replaces an exact text block and refuses ambiguous edits — a block
that occurs more than once needs an explicit expected count.
Terminal processes run behind an injectable executor; the default
spawns real shell processes and buffers their output, so
read_process_output returns only output you have not seen yet.
Two honest simplifications against the toolset this is modelled
on: write_pdf writes the given content as-is (no PDF layout
engine), and search executes synchronously in-process rather than
streaming from a ripgrep subprocess.
Install
npx -y @reneturcios/deskcommand mcp
CLI
deskcommand mcp
deskcommand ls <path>
deskcommand read <path>
deskcommand run <command...>
deskcommand search <path> <pattern>
deskcommand --version
Exit codes: 0 success, 1 operation error, 2 usage error.
MCP tools
26 tools: create_directory, edit_block, force_terminate,
get_config, get_file_info, get_more_search_results,
get_prompts, get_recent_tool_calls, get_usage_stats,
give_feedback_to_desktop_commander, interact_with_process,
kill_process, list_directory, list_processes,
list_searches, list_sessions, move_file, read_file,
read_multiple_files, read_process_output, set_config_value,
start_process, start_search, stop_search, write_file,
write_pdf.
MCP client config:
{
"mcpServers": {
"deskcommand": {
"command": "npx",
"args": ["-y", "@reneturcios/deskcommand", "mcp"]
}
}
}
Docker
docker run -i ghcr.io/cloudcorprecords/deskcommand # MCP server
docker run --rm ghcr.io/cloudcorprecords/deskcommand --version
Development
npm install
npm run build
npm test
MIT license.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.