terminal-emulator-mcp
Related Servers
Alternatives to terminal-emulator-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to programmatically control interactive terminal applications through HT sessions, supporting session management, key sending, snapshots, and command execution.1MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with fully interactive terminal sessions, including TUI support, keyboard control, and screen capture across Windows, Linux, and Mac.MIT

ShellPuppetofficial
AlicenseNot gradedqualityAmaintenanceEnables AI agents to drive real terminal sessions — starting, typing, reading the screen, waiting on prompts and killing processes — while a human watches and can type into the same live session from a browser. Exposes twelve MCP tools for session control, snapshotting, finding text and sharing viewer links.434 npmApache 2.0- AlicenseNot gradedqualityDmaintenanceEnables AI agents to spawn and interact with real terminal sessions, capturing screenshots of rendered TUI output and sharing live sessions for debugging.5 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to launch, drive, and verify Terminal User Interface applications by sending keystrokes and control combinations, capturing screen output, asserting text at exact coordinates, inspecting per-cell colours and cursor position, resizing live sessions, and rendering screenshots or GIFs. Supports multiple concurrent sessions in stream mode for CLI tools or buffer mode for full-screen ncurses-style apps.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to spawn persistent terminal sessions, send keystrokes, read screen state, and assert output, allowing them to interact with stateful terminal applications like vim, htop, and gdb.41 npmMIT
TDQS
Scored across 6 tools
Each tool targets a distinct operation on terminal sessions: listing, starting, observing, sending input, resizing, and closing. There is no overlap or ambiguity between them, and the descriptions clearly differentiate read-only vs. write operations.
All tools follow a consistent verb_noun pattern with a common 'terminal_' prefix (e.g., terminal_start, terminal_snapshot, terminal_close). The naming is uniform and predictable, making it easy for agents to infer tool purpose from the name.
With 6 tools, the server is well-scoped for a terminal emulator. Each tool covers a core aspect of terminal lifecycle management without unnecessary bloat or redundancy, fitting the typical sweet spot for tool count.
The tool surface covers the full lifecycle: create (terminal_start), observe (terminal_snapshot), interact (terminal_input), resize (terminal_resize), destroy (terminal_close), and manage sessions (terminal_list). There are no obvious gaps for the stated purpose.