Skip to main content
Glama
taskhub-sh

Terminal Control MCP

by taskhub-sh

Related Servers

Alternatives to Terminal Control MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to spawn and interact with real terminal sessions, capturing screenshots of rendered TUI output and sharing live sessions for debugging.
      6 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to see and control an existing Linux X11 desktop over SSH by taking screenshots and performing mouse, scroll, typing, and keyboard-shortcut actions across browsers, terminals, file managers, and other apps.
      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
      F
      maintenance
      Enables AI assistants to test Terminal User Interface (TUI) applications by launching, interacting with, and verifying programmatic output and behavior.
      18
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      35 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and automation tools to interact with GUI applications in isolated X11 displays via MCP, supporting input, window management, screenshots, clipboard, and accessibility actions.
      3
      MIT

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: launch creates a session, input sends keystrokes, capture takes screenshots, and close terminates sessions. The descriptions reinforce these distinct roles, making it easy for an agent to select the right tool for any terminal control task.

    Naming Consistency5/5

    All tool names follow a perfect verb_noun pattern with 'terminal_' prefix (terminal_launch, terminal_input, terminal_capture, terminal_close). This consistent naming convention makes the tool set predictable and easy to understand at a glance.

    Tool Count5/5

    Four tools is ideal for this server's purpose of terminal control. Each tool earns its place by covering essential lifecycle operations: create (launch), interact (input), monitor (capture), and destroy (close). No tool feels redundant or missing for basic terminal management.

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for terminal sessions: launch creates, input interacts, capture monitors, and close deletes. There are no obvious gaps—agents can fully manage terminal sessions from creation to termination with all necessary operations available.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues