bravoric-ssh-mcp
Related Servers
Alternatives to bravoric-ssh-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables managing local tmux sessions, windows, and panes over stdio, including listing, creating, renaming, killing, sending keys, and capturing pane output.41 npmMIT
- AlicenseNot gradedqualityBmaintenanceExposes 20 tools over stdio that let coding agents treat any SSH-reachable machine as a local workspace: reading, writing, editing, searching and listing files, running commands and background jobs, driving persistent terminals, and forwarding ports over one pooled connection, with nothing installed on the remote host.295 npm1MIT
- AlicenseAqualityBmaintenanceEnables an agent to administer a Linux host (with first-class Arch support) over SSH through 109 typed tools covering system state, systemd, journal, packages, network, disks, hardware, boot, sessions, users and security, all returning compact JSON. Reads are the default, while mutations require write mode plus a single-use confirmation token, with optional sudo for root-level operations.12329 npm2MIT
- AlicenseAqualityDmaintenanceEnables 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.8MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to spawn, monitor, and control CLI coding agents running in isolated tmux sessions, with verified input injection, redacted pane capture, fleet and per-session state classification, lineage tracking, blocking exec with exit codes, cross-agent messaging, waste analytics, and log/ledger reading. Ownership checks, policy controls, and audit events keep every control action safe by default.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to remotely execute shell commands and transfer files on SSH hosts, including jump-host tunneling, background tasks, resumable transfers, and optional approval of destructive commands, while SSH credentials remain in the local process. It runs over stdio or a streamable HTTP daemon and supports auditing, allow/deny lists, and multiple authentication methods.ISC
TDQS
Scored across 47 tools
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.
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.
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.
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.