mcp2term
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP2TERM_SHELL | No | Shell executable used for commands. | /bin/bash |
| MCP2TERM_PLUGINS | No | Comma-separated dotted module paths to load as plugins. | |
| MCP2TERM_WORKDIR | No | Working directory for commands. | Current directory |
| MCP2TERM_EXTRA_ENV | No | JSON object merged into the command environment. | {} |
| MCP2TERM_INHERIT_ENV | No | When `true`, inherit the parent environment. | true |
| MCP2TERM_COMMAND_TIMEOUT | No | Default timeout in seconds for 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_commandC | Execute a shell command with live stdout/stderr streaming. |
| cancel_commandC | Send a signal to a running command. |
| send_stdinC | Forward input to a running command's stdin pipe. |
| manage_fileC | Create, edit, and inspect files on the remote host including line-based operations. |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: cancel_command stops processes, manage_file handles file operations, run_command executes commands, and send_stdin provides input to running commands. The boundaries are well-defined and unambiguous.
Three tools follow a consistent verb_noun pattern (cancel_command, run_command, send_stdin), but manage_file uses a more general verb that slightly deviates from the others. The naming is still highly readable and mostly consistent.
With 4 tools, this server is well-scoped for remote command and file management. Each tool earns its place by covering essential operations without bloat, making it appropriate for its purpose.
The toolset covers core remote execution workflows: running commands, managing files, and interacting with processes. A minor gap is the lack of a tool for listing or monitoring running processes, but agents can work around this using run_command with appropriate shell commands.