Skip to main content
Glama
votsie

ssh-mcp

by votsie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to ssh-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-ssh-terminal

      zhdkirill
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to have persistent, fully interactive SSH sessions into remote hosts, behaving like a local terminal.
      23 npm
      1
      MIT

    • fast-mcp-ssh

      klNuno
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to securely execute commands on remote hosts via SSH and SFTP, with persistent shells, file transfers, screenshots, and an audit log.
      1
      MIT

    • MCP ShellKeeper

      tranhuucanh
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to maintain persistent SSH terminal sessions and transfer files to/from remote servers. Allows stateful command execution, natural language server management, and seamless file operations through SSH connections.
      7 npm
      37
      MIT

    • ssh-pro-mcp

      a1113622001
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage remote servers via SSH, including command execution, multi-host batch operations, SFTP file transfer, background job handling, DevOps diagnostics, port tunneling, and safety guardrails like high-risk command blocking and read-only mode.
      MIT

    • SSH MCP Server

      uarlouski
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to securely execute commands, transfer files, and manage port forwarding on remote servers via SSH.
      91 npm
      37
      Apache 2.0
    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

    B3.4/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (run vs shell, upload vs file_write, notes vs facts), but ssh_run and ssh_shell_open could be confused for interactive vs non-interactive execution, and ssh_upload vs ssh_file_write overlap in file transfer. The descriptions help disambiguate, but the boundaries require careful reading.

    Naming Consistency4/5

    The naming follows a consistent ssh_<verb>_<noun> pattern (ssh_run, ssh_upload, ssh_shell_open, ssh_tunnel_open). Minor deviations like ssh_status, ssh_guide, and ssh_import_legacy break the verb_noun pattern slightly, but the overall convention is predictable.

    Tool Count3/5

    29 tools is on the heavy side for an SSH server, but the breadth is justified by covering connections, file operations, interactive shells, tunnels, notes, and history. It feels comprehensive rather than bloated, though some tools (ssh_keys_list, ssh_shell_resize) are niche.

    Completeness5/5

    The tool surface covers the full SSH lifecycle: connection management (connect, disconnect, save, forget), file operations (upload, download, read, write, list, copy), interactive sessions (open, send, read, resize, close), tunnels (open, close), and auxiliary data (notes, facts, history, keys). No obvious dead ends for common workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources