Host Terminal MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Override permission mode for this session. Options: allowlist, ask, allow_all | |
| config | No | Path to configuration file (default: ~/.config/host-terminal-mcp/config.yaml) | |
| allow-dir | No | Add allowed directory (can be used multiple times) |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_commandA | Execute a terminal command on the host machine. Commands are subject to permission controls based on configuration. Read-only commands like ls, cat, git status are generally allowed by default. Use 'cd' as a separate command or specify working_directory parameter. |
| change_directoryB | Change the current working directory for subsequent commands. |
| get_current_directoryB | Get the current working directory. |
| approve_commandA | Approve a command that requires permission. This is used when permission_mode is 'ask' and a command is not in the allow list. The command will be approved for this session only. |
| get_permission_statusA | Get information about the current permission mode and allowed commands. |
| set_permission_modeA | Change the permission mode. Modes: 'allowlist' (only allow listed commands), 'ask' (prompt for unlisted commands), 'allow_all' (allow all commands - use with caution!) |
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 6 tools
Each tool has a clearly distinct purpose with no overlap. approve_command handles permissions, change_directory and get_current_directory manage directories, execute_command runs commands, and get_permission_status and set_permission_mode control permission settings. The descriptions clearly differentiate their functions.
All tool names follow a consistent verb_noun pattern (e.g., approve_command, change_directory, execute_command). The naming is uniform across all six tools, using snake_case throughout without any deviations or mixed conventions.
With 6 tools, this is well-scoped for a terminal management server. Each tool serves a specific, necessary function in the domain of executing commands and managing permissions, with no redundant or missing tools that would suggest an inappropriate count.
The tool set provides complete coverage for terminal operations and permission management. It includes command execution, directory navigation, permission status checks, and mode settings, with no obvious gaps. The domain is fully covered, allowing agents to handle all core workflows without dead ends.