Skip to main content
Glama
gethshap

Windows Telnet MCP

by gethshap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Windows Telnet MCP

No user-submitted related servers found.

    Related Servers

    • Terminal MCP

      Hor1zonZzz
      A
      license
      A
      quality
      D
      maintenance
      Enables management of visible, interactive terminal sessions across platforms (macOS, Windows, Linux, WSL). Supports creating, executing commands, capturing output, and managing multiple terminal windows simultaneously.
      5
      1
      MIT

    • portal

      tiefeiyu
      A
      license
      A
      quality
      A
      maintenance
      Enables 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.
      13
      1
      MIT

    • PTY Debug MCP Server

      so2liu
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables spawning, interacting with, and capturing screen output from terminal-based programs for debugging PTY/TTY/TUI applications.
      6 npm
      7
      MIT

    • Tmux MCP Server

      MediocreTriumph
      A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      8
      8 npm
      MIT

    • MCP Remote Shell

      oceanromain
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables remote shell control of Linux and network devices via SSH/Telnet, with session management and file transfer capabilities.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources