A
licenseNot graded
qualityC
maintenanceMCP server that lets AI agents see and interact with terminal/CLI applications through virtual terminals and PNG screenshots.
103 npm
MIT
terminal-use
Related Servers
Alternatives to terminal-use
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server that gives AI agents real interactive terminal sessions for running REPLs, SSH, database clients, and any interactive CLI with clean text output and smart completion detection.787 npm20MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that lets an agent drive CLI and TUI programs in a real pseudo-terminal, sending keys, text, mouse events and resizes and getting back text or PNG screenshots it can read. Sessions persist in a background daemon, so one terminal can be driven across many tool calls without restarting.MIT
- AlicenseAqualityAmaintenanceA local Python MCP server for driving, perceiving, and rendering terminal programs, using a pluggable PTY and pyte screen model to let AI agents interact with real TUIs.1441 PyPI6MIT
- AlicenseBqualityDmaintenanceLocal + remote terminal interaction control MCP Server. Lets AI agents control interactive TUI programs the way a human would.298 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server that lets AI agents launch, interact with, and inspect Textual TUI applications headlessly.124MIT
TDQS
A4.1/5.0
Scored across 13 tools
Disambiguation4/5
Each tool has a clearly distinct purpose: session lifecycle (create/destroy/list/reset/resize), input (type/press/click/scroll/batch), output (read/screenshot), and synchronization (wait). The main overlap is terminal_batch, which can perform everything type/press/click/scroll do, but descriptions explicitly steer the agent (batch for known sequences, individual tools when you need to look between steps), so confusion is limited.
Naming Consistency5/5
Every tool follows the same terminal_<verb> snake_case pattern (terminal_create, terminal_read, terminal_wait, etc.), with no deviations in case or verb style. The naming is entirely predictable.
Tool Count5/5
13 tools is comfortably within the ideal 3-15 range for a terminal automation server. Each tool maps to a genuine, non-redundant capability (session management, multiple input modalities, output capture, and blocking waits).
Completeness4/5
The surface covers the full session lifecycle (create/destroy/list/reset/resize) plus input, output, and synchronization primitives, which is close to complete for driving a terminal. Minor gaps remain, such as no standalone paste tool outside batch and no explicit signal/interrupt tool beyond terminal_press Ctrl+C.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive