Claude Desktop Commander MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_commandB | Execute a terminal command with timeout. Command will continue running in background if it doesn't complete within timeout. |
| read_outputC | Read new output from a running terminal session. |
| force_terminateC | Force terminate a running terminal session. |
| list_sessionsB | List all active terminal sessions. |
| list_processesA | List all running processes. Returns process information including PID, command name, CPU usage, and memory usage. |
| kill_processA | Terminate a running process by PID. Use with caution as this will forcefully terminate the specified process. |
| block_commandB | Add a command to the blacklist. Once blocked, the command cannot be executed until unblocked. |
| unblock_commandB | Remove a command from the blacklist. Once unblocked, the command can be executed normally. |
| list_blocked_commandsB | List all currently blocked commands. |
| read_fileA | Read the complete contents of a file from the file system. Handles various text encodings and provides detailed error messages if the file cannot be read. Only works within allowed directories. |
| read_multiple_filesA | Read the contents of multiple files simultaneously. Each file's content is returned with its path as a reference. Failed reads for individual files won't stop the entire operation. Only works within allowed directories. |
| write_fileA | Completely replace file contents. Best for large changes (>20% of file) or when edit_block fails. Use with caution as it will overwrite existing files. Only works within allowed directories. |
| create_directoryA | Create a new directory or ensure a directory exists. Can create multiple nested directories in one operation. Only works within allowed directories. |
| list_directoryA | Get a detailed listing of all files and directories in a specified path. Results distinguish between files and directories with [FILE] and [DIR] prefixes. Only works within allowed directories. |
| move_fileA | Move or rename files and directories. Can move files between directories and rename them in a single operation. Both source and destination must be within allowed directories. |
| search_filesC | Recursively search for files and directories matching a pattern. Searches through all subdirectories from the starting path. Only searches within allowed directories. |
| get_file_infoA | Retrieve detailed metadata about a file or directory including size, creation time, last modified time, permissions, and type. Only works within allowed directories. |
| list_allowed_directoriesB | Returns the list of directories that this server is allowed to access. |
| edit_blockA | Apply surgical text replacements to files. Best for small changes (<20% of file size). Multiple blocks can be used for separate changes. Will verify changes after application. Format: filepath, then <<<<<<< SEARCH, content to find, =======, new content, >>>>>>> REPLACE. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Every tool has a clearly distinct purpose with no significant overlap. For example, read_file and read_multiple_files are clearly differentiated by single vs. batch operations, while edit_block and write_file are distinguished by surgical vs. complete replacement use cases. The command blocking tools (block_command, unblock_command, list_blocked_commands) form a coherent subsystem without confusion.
All tools follow a consistent verb_noun pattern with perfect consistency throughout. The naming convention is uniformly descriptive and predictable, making it easy to understand each tool's function at a glance. Examples include list_directory, create_directory, move_file, and search_files.
With 19 tools, the count is slightly high but reasonable for a desktop command and file management server. The tools cover multiple domains (file operations, process management, terminal sessions, command blocking), and most tools earn their place. A slight reduction might improve focus, but the scope justifies the current count.
The tool surface provides comprehensive coverage for desktop command and file management operations. It includes full CRUD for files (create_directory, read_file, edit_block/write_file, move_file), process lifecycle management (list_processes, kill_process), terminal session control (execute_command, list_sessions, read_output, force_terminate), and command security (block/unblock). No obvious gaps exist for the server's stated purpose.