PiloTY
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_sessionA | Create a PTY session with an explicit working directory. MCP does not provide a standard field for the client's current working
directory. The caller must provide Args: session_id: Stable identifier for this PTY session. cwd: Working directory for the session's shell. description: Free-form description of what this session is doing (for humans). |
| send_lineA | Send one newline-terminated line to a stateful PTY session. Requires an existing session created via After sending
Common SSH pattern:
|
| send_textA | Send raw text to a stateful PTY session without adding a newline. Requires an existing session created via After sending
|
| send_passwordA | Send a password plus newline. Requires an existing session created via Security model:
After sending
|
| send_controlA | Send a control character to the terminal. Requires an existing session created via Keys:
After sending the control character, this drains newly produced PTY bytes
until the PTY is silent for
|
| wait_for_outputA | Wait for newly arriving PTY output without sending input. Requires an existing session created via This waits for new PTY bytes to arrive. After the first new output is
observed, it continues draining until the PTY is silent for
If you need to wait specifically for a shell prompt, use
|
| snapshot_screenA | Get the current VT100-rendered terminal screen snapshot. Requires an existing session created via This is a passive snapshot. It does not ingest new PTY bytes. |
| snapshot_scrollbackA | Get rendered terminal scrollback. Requires an existing session created via This is a passive snapshot. It does not ingest new PTY bytes. |
| clear_scrollbackB | Clear rendered scrollback history while preserving current screen. Requires an existing session created via |
| wait_for_regexA | Wait for a regex match in rendered text and/or newly arriving PTY bytes. Requires an existing session created via This first checks already rendered scrollback, then waits on new PTY output.
|
| wait_for_shell_promptA | Wait until a shell prompt is detected. Requires an existing session created via This repeatedly ingests new PTY output and re-runs prompt detection until a
shell prompt is visible or until If the remote shell uses a customized prompt that the default heuristics
misclassify, set
|
| get_metadataB | Get metadata for an existing PTY session. Requires an existing session created via |
| list_sessionsD | – |
| configure_sessionA | Update session metadata and shell prompt detection.
This can be called before a session exists; values are stored by |
| send_signalB | Send an OS signal to the foreground process in a session. Requires an existing session created via |
| transcriptC | Get the transcript file path for this session. |
| terminateB | Terminate a PTY session. Future calls using the same |
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 17 tools
Each tool has a clearly distinct purpose: session lifecycle, input methods (line, text, control, password, signal), output retrieval (snapshots, transcript), and waiting mechanisms (output, regex, prompt). No overlap or ambiguity.
All tools use a consistent verb_noun snake_case pattern (e.g., create_session, send_line, wait_for_shell_prompt). No mixing of conventions.
17 tools are well-scoped for a PTY management server, covering all necessary interactions without bloat. Each tool serves a distinct, necessary function.
The tool set covers session lifecycle, multiple input modes, output retrieval, and waiting for various states. It includes password handling and signal sending, appearing complete for typical terminal interaction use cases.