cmd-line-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CMD_LINE_MCP_CONFIG | No | Path to a custom configuration JSON file. | |
| CMD_LINE_MCP_COMMANDS_READ | No | Comma-separated list of allowed read commands (e.g., awk,jq,wc). | |
| CMD_LINE_MCP_COMMANDS_WRITE | No | Comma-separated list of allowed write commands. | |
| CMD_LINE_MCP_COMMANDS_SYSTEM | No | Comma-separated list of allowed system commands. | |
| CMD_LINE_MCP_SECURITY_REQUIRE_SESSION_ID | No | Whether to require a session ID for operations (true/false). Defaults to false. | |
| CMD_LINE_MCP_SECURITY_WHITELISTED_DIRECTORIES | No | Comma-separated list of whitelisted directories (e.g., /home,/tmp). | |
| CMD_LINE_MCP_SECURITY_ALLOW_COMMAND_SEPARATORS | No | Whether to allow command separators like ; or && (true/false). | |
| CMD_LINE_MCP_SECURITY_AUTO_APPROVE_DIRECTORIES_IN_DESKTOP_MODE | No | Whether to auto-approve directories when running in desktop mode (true/false). |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_commandC | Execute a Unix/macOS terminal command. |
| execute_read_commandA | Execute a read-only Unix/macOS terminal command (ls, cat, grep, etc.). |
| list_available_commandsB | List all available commands by category. |
| get_command_helpB | Get detailed help about command capabilities and usage. |
| approve_command_typeC | Approve a command type for the current session. |
| approve_directoryC | Approve access to a directory for the current session. |
| list_directoriesC | List all whitelisted and approved directories. |
| get_configurationC | Get the current configuration settings. |
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 8 tools
Most tools have distinct purposes, but there is some potential overlap between 'execute_command' and 'execute_read_command' as both execute commands, which could cause confusion about when to use each. The other tools are clearly differentiated by their specific functions like approval, listing, and configuration.
The naming follows a consistent verb_noun pattern throughout, such as 'approve_command_type', 'execute_command', and 'list_directories'. However, there is a minor deviation with 'get_command_help' and 'get_configuration' using 'get' instead of a more action-oriented verb, but overall the pattern is predictable and readable.
With 8 tools, the count is well-scoped for a command-line MCP server, covering key operations like execution, approval, listing, and configuration without being overwhelming. Each tool appears to serve a necessary function in managing and executing commands.
The toolset provides good coverage for command-line operations, including execution, approval, listing, and help. A minor gap is the lack of tools for updating or deleting configurations or approvals, but agents can likely work around this with the existing tools for most workflows.