Skip to main content
Glama

Related Servers

Alternatives to mcp-ssh-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Bridges AI coding agents into Local and Remote-SSH/WSL/Dev Container VS Code windows, letting them read, edit, and search files, run commands and manage background tasks, and inspect live editor state, selections, and LSP diagnostics without installing anything on the remote host.
      12
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents on a remote server to operate a local computer over an SSH tunnel, including reading and writing code, searching files, and running commands.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding tools to read, write, search, and list files and run commands or long background jobs on a remote machine through a single persistent SSH connection, avoiding the process-spawn and handshake cost of a fresh connection per call. Also supports TTY programs via tmux and remote job status checks that survive client restarts.
      12
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables local AI coding assistants to operate remote Linux EDA clusters over persistent SSH/SCP for digital IC design, simulation, formal property verification, UVM testbench generation, static linting, and Git-backed workspace synchronization.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to perform operations on remote servers by reusing SSH sessions from a local desktop app, including command execution, file upload/download, and project document management with security controls.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      SSH MCP Server lets you manage remote Linux servers through natural language in VS Code Copilot Chat. Instead of switching to a terminal and remembering SSH commands
      23
      MIT

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: connect_ssh for establishing the connection, execute_command for running arbitrary commands, and read_file/write_file/list_directory for file system operations. There is no ambiguity between the tools, and their purposes are self-evident from their names.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: connect_ssh, execute_command, read_file, write_file, list_directory. This makes the API predictable and easy to understand.

    Tool Count5/5

    With five tools, the server is well-scoped and each tool serves a distinct, necessary function for SSH operations. The count falls within the ideal 3-15 range and does not feel either bloated or sparse.

    Completeness4/5

    The tool set covers essential SSH operations: connect, execute commands, read/write files, and list directories. While a disconnect tool or more advanced file operations (e.g., stat, upload) are missing, these can be worked around via execute_command, so the gaps are minor.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data