PTY MCP Server
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": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pty_spawnA | Spawns a new PTY (pseudo-terminal) session that runs in the background. Unlike synchronous bash commands, PTY sessions persist and allow you to:
Returns the session ID, which you can use with other pty_* tools. |
| pty_readA | Reads output from a PTY session's buffer. The PTY maintains a rolling buffer of output lines. Use offset and limit to paginate through the output. Two modes:
The buffer stores up to PTY_MAX_BUFFER_LINES (default: 50000) lines. Older lines are discarded when the limit is reached. |
| pty_writeA | Sends input data to an active PTY session. Use this tool to:
Common escape sequences:
|
| pty_listA | Lists all PTY sessions (active and exited). Use this tool to:
Sessions remain in the list after exit until explicitly cleaned up with pty_kill, allowing you to read their output logs. |
| pty_killA | Terminates a PTY session and optionally cleans up its buffer. Behavior:
Use cleanup=false if you might want to read the output later. Use cleanup=true when you're done with the session entirely. To send Ctrl+C instead of killing, use pty_write with data="\x03" |
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: pty_spawn creates sessions, pty_list enumerates them, pty_write sends input, pty_read retrieves output, and pty_kill terminates sessions. The descriptions reinforce these distinct roles, making tool selection unambiguous for an agent.
All tools follow a consistent 'pty_' prefix with descriptive action suffixes (spawn, list, write, read, kill) in snake_case. This uniform pattern makes the tool set predictable and easy to navigate, with no deviations in naming conventions.
With 5 tools, this server is well-scoped for managing pseudo-terminal sessions. Each tool serves a clear, necessary function (create, list, input, output, destroy), providing complete lifecycle coverage without bloat or redundancy, which is ideal for the domain.
The tool set offers complete CRUD/lifecycle coverage for PTY management: spawn (create), list (read), write (update input), read (retrieve output), and kill (delete). There are no obvious gaps; agents can fully manage sessions from creation to termination with all necessary interactions.