Skip to main content
Glama
hypnosis

SSH MCP Server

by hypnosis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to SSH MCP Server

No user-submitted related servers found.

    Related Servers

    • ssh-mcp-server

      ZachFlint
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to securely execute remote SSH commands, perform file transfers, and monitor system status through a standardized interface. It features robust security controls including command whitelisting, blacklisting, and credential isolation to prevent unauthorized operations.
      10
      22 npm
      MIT

    • vps-remote

      MohamedCHAMI
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to execute SSH commands and transfer files to and from remote servers, supporting remote server management and seamless session transfer to a VPS.
      -
    • cygnus-ssh-mcp by cygnussystems

      cygnus-ssh-mcpofficial

      cygnussystems
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to manage remote servers via SSH with 43 specialized tools for command execution, file editing, directory operations, and background tasks across Linux, macOS, and Windows.
      44
      5
      GPL 3.0

    • connect-to-server-mcp

      vstlmkh
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to securely connect to and manage remote servers via SSH, with tools for running commands, file operations, log inspection, service management, and system monitoring under configurable access controls and audit logging.
      12
      617 npm
      MIT
    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

    A4.2/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: file read/write/list/upload/download, job status/output/list/kill, log tail/search, and system snapshot/audit/disk/service checks are clearly separated. Cross-references such as ssh_file_read vs ssh_download and ssh_snapshot vs ssh_audit_baseline reinforce rather than blur the boundaries. ssh_exec is explicitly positioned as a last-resort generic tool, reducing overlap.

    Naming Consistency4/5

    All tools share the ssh_ prefix and snake_case, and most follow a domain_action pattern like ssh_file_read, ssh_job_status, and ssh_log_search. A few one-offs such as ssh_snapshot, ssh_monitor, ssh_upload, and ssh_audit_baseline break the otherwise predictable pattern, though they remain readable and recognizable.

    Tool Count4/5

    At 18 tools, the set is slightly above the typical 3-15 range, but it covers a broad SSH operations domain: execution, files, transfers, detached jobs, logs, monitoring, TLS, disk, and services. Each tool has a distinct role and none feels redundant, so the count is reasonable for the stated scope.

    Completeness4/5

    The tool surface covers the main workflows: command execution, file read/write/list/transfer, detached job lifecycle, log tailing/searching, and system/health inspection. Obvious gaps like a dedicated file delete or service start/stop are absent, but ssh_exec provides a universal fallback, so agents can work around those missing operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources