Command-Line MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CMD_LINE_MCP_COMMANDS_READ | No | Comma-separated list of read commands to add to the defaults | |
| CMD_LINE_MCP_COMMANDS_WRITE | No | Comma-separated list of write commands to add to the defaults | |
| CMD_LINE_MCP_COMMANDS_SYSTEM | No | Comma-separated list of system commands to add to the defaults | |
| CMD_LINE_MCP_COMMANDS_BLOCKED | No | Comma-separated list of blocked commands to add to the defaults | |
| CMD_LINE_MCP_SECURITY_REQUIRE_SESSION_ID | No | Whether to require a session ID for commands | |
| CMD_LINE_MCP_SECURITY_WHITELISTED_DIRECTORIES | No | Comma-separated list of directories that can be accessed without approval | |
| CMD_LINE_MCP_SECURITY_ALLOW_COMMAND_SEPARATORS | No | Whether to allow command chaining with separators like |, ;, & | |
| CMD_LINE_MCP_SECURITY_AUTO_APPROVE_DIRECTORIES_IN_DESKTOP_MODE | No | Whether to automatically approve directories when using Claude Desktop |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_commandC | Execute a Unix/macOS terminal command. Args: command: The command to execute session_id: Optional session ID for permission management Returns: A dictionary with command output and status |
| execute_read_commandB | Execute a read-only Unix/macOS terminal command (ls, cat, grep, etc.). Args: command: The read-only command to execute session_id: Optional session ID for permission management Returns: A dictionary with command output and status |
| list_available_commandsB | List all available commands by category. Returns: A dictionary with commands grouped by category |
| get_command_helpB | Get detailed help about command capabilities and usage. This tool provides comprehensive information about:
Returns: A dictionary with detailed information about command capabilities and usage |
| approve_command_typeB | Approve a command type for the current session. Args: command_type: The command type to approve (read, write, system) session_id: The session ID remember: Whether to remember this approval for the session Returns: A dictionary with approval status |
| approve_directoryC | Approve access to a directory for the current session. Args: directory: The directory to approve access to session_id: The session ID remember: Whether to remember this approval for the session Returns: A dictionary with approval status |
| list_directoriesB | List all whitelisted and approved directories. Args: session_id: Optional session ID to get session-specific approvals Returns: A dictionary with globally whitelisted and session-approved directories |
| get_configurationB | Get the current configuration settings. Returns: 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
Tools have mostly distinct purposes: execute_command and execute_read_command overlap in executing commands, but the read-only distinction is meaningful for permission safety. Approval tools are clearly differentiated by type vs directory. Help and listing tools are distinct. No major confusion.
All tools follow a consistent verb_noun pattern (get_, approve_, execute_, list_). No mixing of conventions.
8 tools is well-scoped for a command-line execution server with permission management. Each tool serves a clear purpose.
Core functionality (execute, approve, list, get help/config) is covered. However, there is no tool to revoke approvals or reset session permissions, which could be a minor gap for full lifecycle management.