Skip to main content
Glama

Related Servers

Alternatives to bravoric-ssh-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables programmatic control over tmux terminal sessions for SSH access, command execution, and terminal automation. Supports creating sessions, sending commands, capturing output, and managing multiple panes for interactive debugging and monitoring.
      8
      5 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables managing SSH-managed clusters with tools for executing commands, file operations, and tmux sessions across multiple nodes.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent SSH/PTY sessions to a bastion host with asset discovery, permission-gated audited command execution, and batch operations across multiple targets.
      1
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      Enables managing remote hosts from ~/.ssh/config over OpenSSH, including availability checks, command execution with sudo and timeouts, background jobs, SSH config and known_hosts management, and llms.txt-based documentation retrieval.
      19
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Remote execution layer for agentic systems exposing 64 production tools via MCP for file, network, system, text, git, crypto, and monitoring operations.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables SSH command execution, file uploads/downloads, and multi-server management with zero-config inline credentials, supporting async jobs and AI-readable output.
      15 npm
      2
      AGPL 3.0

    TDQS

    C2.5/5.0

    Scored across 47 tools

    Disambiguation3/5

    Many tools are clearly distinct (e.g., ping vs list_hosts vs create_session), but several overlapping pairs exist: run_command vs run_command_all vs run_command_many, broadcast vs broadcast_wait, list_tunnels vs list_tunnels_all, and list_audit_logs vs list_remote_audit_logs. Descriptions help but don't fully eliminate ambiguity, especially around batch vs single-host variants.

    Naming Consistency4/5

    The vast majority of tools follow a consistent verb_noun convention (list_hosts, get_host, create_session, kill_session, etc.). Minor deviations appear in compound names like hosts_summary (noun_verb) and ping_all, but overall it's predictable.

    Tool Count2/5

    47 tools is excessive for the apparent scope and goes well beyond the typical 3-15 range. Many tools are thin wrappers (send_enter, send_keys, send_raw) that could be consolidated, making the surface feel heavy and unwieldy.

    Completeness4/5

    Coverage is broad: host management, tmux sessions/windows/panes, tunnels, snippets, rotations, audit logs, and diagnostics are all present. A few gaps exist (e.g., no explicit update_host or snippet editing), but the lifecycle for most resources is covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues