Skip to main content
Glama
Sanjay-dev22

visible-terminal-mcp

by Sanjay-dev22

Related Servers

Alternatives to visible-terminal-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to drive genuine interactive Windows console sessions through ConPTY, so they can launch PowerShell, pwsh or CMD, send keystrokes, answer prompts, watch rendered screens and block until output matches. Multiple persistent shells can run in parallel, supporting live input, incremental reads, interrupts and window resizing.
      10
      MIT
    • 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
      A
      maintenance
      Enables AI agents to drive native Windows apps and headed browsers inside a hidden child desktop session with its own screen, pointer and keyboard focus. Provides tools for screenshots, mouse/keyboard input, accessibility inspection, UI waits, display changes, Android emulators, application launches and cancellable command jobs, so the user's own desktop stays free.
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI models to control a local Windows desktop by moving the cursor, clicking, scrolling, typing Unicode text, sending key chords, and capturing screenshots. Runs natively on Windows with minimal latency and no heavy dependencies such as Python, PyAutoGUI, or Docker.
      58 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to see and drive a live Windows remote desktop session inside VS Code — capturing screenshots, clicking, moving, dragging and scrolling, typing Unicode text, sending key combinations, syncing the clipboard, and running PowerShell or cmd commands on the remote machine with text output and exit codes.
      MIT

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool maps to a distinct lifecycle action on a visible terminal: spawn, send, read, and close. There is no overlap in purpose, and the descriptions make the boundaries between input, output, and process management clear.

    Naming Consistency5/5

    All tools use a consistent vterm_verb pattern: vterm_spawn, vterm_send, vterm_read, vterm_close. The shared prefix and short action verbs are predictable and readable.

    Tool Count5/5

    Four tools are well-scoped for a focused visible-terminal controller. Each tool earns its place in the create/send/read/close lifecycle, with no redundant operations.

    Completeness4/5

    The core lifecycle for a visible terminal is covered: opening, typing into, reading from, and closing a window. Minor gaps exist, such as explicit waiting for command completion or listing active terminal windows, but agents can work around them with repeated reads.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues