termcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAX_TIMEOUT_MS | No | Maximum command timeout in ms. | 300000 |
| MAX_OUTPUT_CHUNK | No | Output chunk size before truncation. | 50000 |
| TERMCP_WORKSPACE | No | Root directory for file operations. | $HOME |
| DEFAULT_TIMEOUT_MS | No | Default command timeout in ms. | 30000 |
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 |
|---|---|
| run_commandB | Execute a shell command locally. Returns stdout, stderr, and exit code. |
| run_sequenceB | Execute multiple shell commands in sequence. Supports variable capture ($PREV, $STEP{n}). |
| read_fileC | Read the contents of a text file. |
| write_fileA | Write content to a file. Creates parent directories if needed. |
| list_filesB | List files and directories in a path. |
| search_filesB | Search for a pattern in files. Uses ripgrep if available, falls back to grep. |
| get_environmentA | Get info about the local environment: OS, installed tools, disk usage. |
| get_audit_logB | Get the audit log of commands executed. Supports filtering. |
| start_processA | Start a long-running background process. Returns process_id and pid. |
| poll_outputC | Poll output from a background process. |
| kill_processC | Kill a background process by process_id. |
| create_sessionA | Create a stateful tmux session with persistent cwd and environment. |
| destroy_sessionC | Kill a tmux session. |
| read_outputA | Read output from a specific byte offset. Used for truncated output. |
| get_server_infoA | Get server info: version, uptime, workspace, active processes. |
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 15 tools
Most tools have clearly distinct purposes (file ops vs command execution vs process lifecycle vs sessions). Some overlap exists between run_command and run_sequence, and between poll_output and read_output, but descriptions provide enough differentiation to avoid major confusion.
All tool names follow a consistent verb_noun snake_case pattern (run_command, read_file, start_process, etc.). No mixing of conventions or vague verbs.
15 tools is within the reasonable range for a terminal/shell server covering command execution, file operations, process management, and sessions. Slightly at the upper bound, but each tool appears to earn its place.
Core workflows are covered: sync/async command execution, file read/write/list/search, process lifecycle, session management, and environment info. Minor gaps exist such as no file delete/move/copy operations and no explicit way to send input to a running process or session.