Windows Telnet MCP
Related Servers
Alternatives to Windows Telnet MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables management of visible, interactive terminal sessions across platforms (macOS, Windows, Linux, WSL). Supports creating, executing commands, capturing output, and managing multiple terminal windows simultaneously.51MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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.2MIT
- AlicenseAqualityAmaintenanceEnables interaction with long-running interactive programs such as SSH, GDB, and REPLs. Provides tools to start, monitor, control, read/write I/O for these processes.131MIT
- AlicenseNot gradedqualityCmaintenanceEnables spawning, interacting with, and capturing screen output from terminal-based programs for debugging PTY/TTY/TUI applications.6 npm7MIT
- AlicenseAqualityBmaintenanceEnables agents to launch and control interactive terminal sessions, inspecting screen text and formatting while sending keyboard and mouse input. Supports real pseudoterminals with resizing, snapshots, and session lifecycle management.6291 npmApache 2.0
- AlicenseAqualityDmaintenanceEnables programmatic control over tmux terminal sessions for SSH access, command execution, and terminal automation. Supports creating sessions, sending commands, capturing output, and managing multiple panes for interactive debugging and monitoring.810 npmMIT
TDQS
Scored across 10 tools
Each tool targets a distinct operation: status/check/list cover different aspects of session state and capability, while read/wait_for_text/send/key separate reading, polling, text injection, and named key injection. There is no meaningful overlap that would confuse an agent.
All tools share a consistent telnet_ prefix followed by a clear verb or verb phrase, such as start, close, send, read, list, and wait_for_text. The naming pattern is uniform and predictable across the entire set.
Ten tools is well-scoped for controlling a visible Windows Telnet client: session lifecycle, I/O, waiting, focusing, and diagnostics are all represented without unnecessary duplication. Each tool contributes a distinct capability.
The toolset covers the full interaction lifecycle: starting a session, connecting, sending input, reading output, waiting for expected text, sending special keys, listing sessions, checking readiness, focusing, and closing. No obvious gap prevents an agent from automating a Telnet workflow.