terminal-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEFAULT_DIR | No | Default working directory for local commands. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_commandC | Execute commands on remote hosts or locally (This tool can be used for both remote hosts and the current machine) |
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 1 tool
There is only one tool, so no ambiguity exists between tools. The tool's purpose is clearly stated to execute commands on remote or local hosts.
The single tool is named 'execute_command', which follows a clear verb_noun pattern. Consistency is trivially maintained with only one tool.
The server provides a single tool, which feels thin for a terminal server. While the tool is broad, additional tools for file operations or process management would be expected.
The tool covers basic command execution, which is the core functionality. However, it lacks features like interactive session handling, background process management, or file transfer, which are common gaps for terminal servers.