Skip to main content
Glama
hugo94z

mcp-interactive-terminal

by hugo94z

Related Servers

Alternatives to mcp-interactive-terminal

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with fully interactive terminal sessions, including TUI support, keyboard control, and screen capture across Windows, Linux, and Mac.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with interactive CLI processes via a real PTY, allowing them to send keystrokes, read screen output, and handle interactive prompts.
      4 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to spawn and control persistent local shells, SSH sessions, REPLs, debuggers, and serial/UART devices with zero-loss output capture, timestamped history, and atomic expect matching for command execution and prompt synchronization.
      12
      18 PyPI
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A PTY-based MCP server providing persistent, interactive shell sessions with strong Windows support, enabling AI agents to run commands, handle interactive tools, and manage large output across MCP-compatible clients.
      303 npm
      12
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with persistent, interactive pseudo-terminal sessions for running CLI tools, SSH, and AWS SSM, including support for prompts, concurrent commands, and a live web TUI.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to fully interact with console applications, monitor output, detect errors, and automate terminal workflows across multiple sessions. Similar to how Playwright works for web browsers but for command-line interfaces.
      138 npm
      52
      MIT

    TDQS

    A4.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: lifecycle (start/stop/list/resize), input (send/interrupt), and output (read/screen/wait/exec). The potentially overlapping read vs. screen and wait vs. read pairs are explicitly differentiated in their descriptions (raw incremental vs. rendered VT view; blocking vs. immediate).

    Naming Consistency5/5

    Every tool follows the same terminal_<verb> snake_case pattern with no exceptions. The verb choices are predictable and consistent across the set.

    Tool Count5/5

    Ten tools is well-scoped for interactive terminal control, with each one covering a necessary operation (lifecycle, input, output, waiting, rendering). No redundant or filler tools.

    Completeness4/5

    The surface covers the full interactive lifecycle: start/stop, send/interrupt, read/screen/wait, resize, plus a one-shot exec for non-interactive commands. Minor gaps exist, such as no session rename or explicit scrollback/buffer clearing, but core workflows are fully covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues