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
      11 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.
      133 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

    A4.1/5.0

    Scored across 46 tools

    Disambiguation4/5

    Most tools target clearly distinct resource+action pairs across well-separated namespaces (conn, host, file, dir, cmd, task, archive). However, a few clusters overlap: ssh_dir_remove vs ssh_dir_delete vs ssh_dir_batch_delete_files all remove directories/files, and ssh_file_replace_line_multi vs ssh_file_delete_line_by_content are near-subsets of each other. Descriptions do disambiguate these, but boundaries require careful reading.

    Naming Consistency4/5

    The ssh_<namespace>_<verb>_<noun> pattern is broadly consistent across file/dir/cmd/task/archive tools. Deviations exist: host management is split between the ssh_conn_ prefix (ssh_conn_add_host) and the ssh_host_ prefix (ssh_host_update, ssh_host_remove, ssh_host_list), and ssh_file_delete_line_by_content doesn't mirror the ssh_file_replace_line structure. Still readable and mostly predictable.

    Tool Count3/5

    46 tools is well above the comfortable range and pushes into heavy territory. For a full-featured remote-shell server spanning connection, host, file, directory, command, task, and archive domains most tools earn their place, but the surface could be consolidated (e.g. three directory-deletion tools, two line-replacement tools).

    Completeness5/5

    Lifecycle coverage is exemplary: connection and host CRUD, file read/write/move/copy/stat plus line-level editing, directory list/mkdir/remove/delete/copy/search/size/transfer, command run/kill/status/output/history, background task launch/status/kill, and archive create/extract. Almost no obvious gaps for an SSH automation server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources