Skip to main content
Glama
ssh-mcp-pro

ssh-mcp-pro

by oaslananka

Related Servers

Alternatives to ssh-mcp-pro

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      SSH-based MCP server that enables remote execution of SSH commands, file transfers, and secure server management via the MCP protocol.
      ISC
    • A
      license
      A
      quality
      A
      maintenance
      SSH automation MCP server that enables Claude and ChatGPT to execute commands, manage files, install packages, and control services on remote servers over SSH — supporting password, key, and agent authentication.
      33
      1,267 npm
      4
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      A Model Context Protocol server for complete shell and SSH mastery, enabling command execution, interactive sessions, file transfer, and port forwarding with auditing and policy controls.
      18
      153 PyPI
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing safe, persistent SSH sessions to remote machines with multi-hop ProxyJump tunneling, SFTP file transfer, and stored host profiles.
      524 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) SSH client server that provides autonomous SSH operations for GitHub Copilot and VS Code. Enable natural language SSH automation without manual prompts or GUI interactions.
      20
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      This is a secure SSH MCP server providing enterprise-grade SSH management with AI assistance, MFA, RBAC, encryption, and compliance auditing.
      MIT

    TDQS

    B3.2/5.0

    Scored across 46 tools

    Disambiguation2/5

    Several tool pairs have blurred boundaries: ssh_list_configured_hosts vs ssh_hosts_list both enumerate hosts, log_tail vs service_logs both read journal entries for a service, and ensure_service overlaps with service_restart/service_stop/service_status. proc_sudo vs proc_exec and ssh_host_inspect vs ssh_resolve_host also require the agent to reason about subtle policy differences rather than purpose.

    Naming Consistency4/5

    The set follows a clear domain-prefix convention (fs_*, ssh_*, service_*, proc_*, tunnel_*, file_*), which makes names scannable and mostly predictable. Minor deviations exist: get_metrics uses verb_noun while peers use noun_verb, os_detect is noun_verb amid prefix-first names, and ssh_list_sessions vs ssh_hosts_list invert the ordering within the same family.

    Tool Count2/5

    46 tools is heavy for what is essentially remote host administration, and the surface shows signs of accretion (multiple logging tools, duplicate host-listing tools, both proc_exec and proc_exec_stream, both connector_status and get_metrics). A single SSH server would be more legible with roughly half this count by merging overlapping families.

    Completeness4/5

    Coverage is broad for the domain: session lifecycle, filesystem CRUD and stats, package/service management, process control, tunnels, transfers, metrics, and a policy/planning layer. Gaps are minor — no user/group or cron/scheduled-task management, and no explicit package listing, but agents can reach those via proc_exec.

    Maintenance

    ActivityActive
    ResponsivenessLimited data