Terminal Control MCP
Related Servers
Alternatives to Terminal Control MCP
No user-submitted related servers found.
Related Servers
- 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 gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with fully interactive terminal sessions, including TUI support, keyboard control, and screen capture across Windows, Linux, and Mac.MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to test Terminal User Interface (TUI) applications by launching, interacting with, and verifying programmatic output and behavior.1219MIT
- AlicenseBqualityBmaintenanceProvides AI agents with a private, headless X11 desktop where they can launch applications, capture screenshots, and control mouse and keyboard without affecting the user's session.23MIT
TDQS
Scored across 4 tools
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.
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.
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.
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.