Skip to main content
Glama
cygnussystems

cygnus-ssh-mcp

Official
by cygnussystems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to cygnus-ssh-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      8 npm
      1
      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.
      132 npm
      37
      Apache 2.0

    • ssh-mcp

      votsie
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to manage remote servers over SSH through interactive terminal emulation, file transfer, tunneling, and persistent server memory.
      29
      1
      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

    B3.1/5.0

    Scored across 44 tools

    Disambiguation2/5

    Several tools overlap heavily: ssh_dir_remove and ssh_dir_delete appear to do the same thing, ssh_cmd_* and ssh_task_* duplicate run/status/kill patterns, and ssh_conn_status vs ssh_conn_host_info vs ssh_conn_is_connected are easily confused. Although some descriptions add nuance, the large number of similar status, kill, search, and delete tools creates substantial ambiguity.

    Naming Consistency4/5

    Tools follow a consistent ssh_<category>_<action> snake_case pattern, with clear categories for conn, cmd, task, file, dir, and archive. Minor deviations like list_tools and ssh_host_disconnect (which is really a connection action) slightly break the pattern, but overall the naming is predictable.

    Tool Count2/5

    44 tools is excessive for an SSH MCP server, well past the 25+ threshold. Many tools are micro-operations that could be consolidated, such as multiple line-editing tools, multiple directory-list tools, and duplicate directory deletion tools.

    Completeness3/5

    The surface covers connection, command, task, file, directory, host, and archive workflows extensively, but notably lacks a basic ssh_file_delete tool and permission/symlink operations. Agents can work around these gaps using ssh_cmd_run, but for a 44-tool file-management server these are significant omissions.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources