Claude Desktop Commander MCP
Related Servers
Alternatives to Claude Desktop Commander MCP
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with B\&R Automation Studio projects by building code, running ARsim simulators, and reading or writing OPC UA variables. It facilitates industrial automation development and real-time variable integration through natural language commands.13MIT
Related Servers
- AlicenseAqualityDmaintenanceAllows Claude to execute terminal commands on your computer and perform file system operations including surgical code editing with diff-based replacements.19158,647 npm7MIT
- FlicenseNot gradedqualityBmaintenanceEnables Claude Desktop or other MCP clients to execute shell commands, read/write files, and list directories on the local machine. Includes basic safety guardrails to block obviously destructive operations.-
- AlicenseAqualityDmaintenanceA server that lets Claude desktop app execute terminal commands on your computer and edit files through Model Context Protocol, featuring command execution, process management, and advanced file operations.19158,647 npm6MIT
- AlicenseAqualityDmaintenanceGive Claude Desktop terminal, filesystem, and background-job access on your local Linux machine. Zero-dependency MCP extension, MIT-licensed.83MIT
- AlicenseNot gradedqualityBmaintenanceExposes an interactive terminal over MCP, enabling remote shell command execution, file operations, and directory management via ChatGPT or Claude Desktop.2MIT
- FlicenseNot gradedqualityBmaintenanceEnables Claude Desktop to execute terminal commands in a controlled workspace via the Model Context Protocol.-
TDQS
Scored across 26 tools
Each tool targets a distinct resource or action: file operations, process management, search, config, and utility functions. Even similar tools like force_terminate (sessions) and kill_process (system processes) are clearly differentiated. No two tools appear to serve the same purpose.
Tool names follow a consistent verb_noun pattern using snake_case (e.g., write_file, start_process, list_directory, get_config). Multi-word names like get_more_search_results still follow the predictable verb_phrase structure. The naming is uniform and intuitive.
With 26 tools, the count is above the typical 3-15 range but justified by the server's broad scope (file management, process control, search, config, and feedback). The tools are organized into clear categories, making the number feel slightly heavy but not excessive.
The tool set covers file read/write/edit/move/info/list, process start/interact/read/terminate/list, search lifecycle, and config get/set. A notable gap is the lack of delete/remove operations for files and directories, which is a common requirement. Process and search coverage is complete.