MCP Terminal
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_processC | Start a long-running process and capture its output to a log file |
| stop_processC | Stop a running process |
| get_logsC | Get logs from a process |
| search_logsC | Search logs for a keyword or regex |
| list_processesB | List all running processes managed by this MCP server |
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 5 tools
Each tool has a clearly distinct purpose with no overlap: get_logs retrieves logs, list_processes enumerates processes, search_logs filters logs, start_process initiates processes, and stop_process terminates them. The descriptions reinforce these boundaries, making misselection unlikely.
All tools follow a consistent verb_noun pattern (e.g., get_logs, list_processes, search_logs, start_process, stop_process), using snake_case throughout. This predictability aids agent comprehension and tool selection.
With 5 tools, the set is well-scoped for terminal/process management, covering core operations (list, start, stop processes, and get/search logs). Each tool earns its place without bloat or thinness.
The tools provide strong coverage for process lifecycle (start, stop, list) and log handling (get, search), but minor gaps exist, such as no tool for restarting processes or managing log files (e.g., delete/rotate). Agents can work around this with existing tools.