cmdshellmcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cmdshellA | Runs one of the configured Linux/Unix commands. Allowed commands: ["ls", "pwd", "date", "cat", "grep", "egrep", "whoami", "head", "tail", "sed", "wc", "file", "du", "df", "free", "ps", "uname", "hostname", "uptime", "w", "last", "mkdir", "cp", "mv", "awk", "jq"] Arguments are checked with _local_path_error: empty arguments, absolute paths, and paths containing a '..' component are rejected. Args: command: The command name (for example, 'ls'). It must be in the allowed commands list. args: A list of command arguments/flags (for example, ['-la', '.txt']). Put a glob in double quotes (for example, ['".txt"']) to pass it literally instead of expanding it into filenames. Pipes and redirects are not allowed. |
| writeFileC | write text into a local file in the current directory |
| readFileA | Read and return a UTF-8 text file beneath the current directory. |
| listFilesC | List entries in a directory beneath the current directory. |
| copyFileC | Copy a local file beneath the configured current directory. |
| moveRenameFileC | Move or rename a local file beneath the configured current directory. |
| deleteFileC | Delete a local file beneath the configured current directory. |
| mkdirC | Create one directory beneath the configured current directory. |
| rmdirA | Remove one empty directory beneath the configured current directory. |
| editFileA | Edits an existing local text file using a sed expression/program. Args: file: Local path of the file to edit, limited to the configured current directory and its descendants. script: The authoritative sed editing expression/program. args: Optional safe sed arguments. Options that enable in-place editing, supply another expression or program file, select other files, or execute commands are not allowed. Before editing, the tool creates the next available numbered backup (.bk1, .bk2,
.bk3, and so on), and never overwrites an existing backup. The source file is
replaced only after sandboxed sed completes successfully. On success, the response
contains a Example: file="src/example.py", script="s/old_name/new_name/g". The resulting
backup might be |
| applyPatchA | Apply
|
| fetchC | fetch a page from a url Args: url: the url to fetch prettify: prettify the retrieved html |
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 12 tools
Each dedicated file tool targets a specific operation (read/write/edit/patch/delete/copy/move/list/mkdir/rmdir), so they are mostly distinct. However, the general cmdshell tool overlaps with many of these (ls, cat, sed, mkdir, cp, mv), which can create ambiguity about whether to use a dedicated tool or a shell command. The detailed descriptions help but overlap remains.
Most file tools use camelCase verb_noun (writeFile, readFile, listFiles, copyFile, etc.), but fetch, cmdshell, mkdir, and rmdir break the pattern with lowercase or Unix-style names. The mix is still readable, but not fully consistent.
12 tools is a reasonable, well-scoped set for a sandboxed file/shell server. Each core operation (create, read, update, delete, directory management, shell, fetch) has a clear place, and the count is within the typical 3-15 range.
The server covers the main file lifecycle: create (writeFile), read (readFile), update (editFile/applyPatch), delete (deleteFile), plus copy, move, directory create/list/remove, and a general command runner. Minor gaps exist (e.g., append-specific operation, metadata/stat, recursive directory deletion), but agents can work around most via cmdshell or editing tools.