ssh-remote
Related Servers
Alternatives to ssh-remote
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding tools to read, write, search, and list files and run commands or long background jobs on a remote machine through a single persistent SSH connection, avoiding the process-spawn and handshake cost of a fresh connection per call. Also supports TTY programs via tmux and remote job status checks that survive client restarts.12MIT
- 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.270 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents on Windows clients to operate on Unix file servers through one long-lived SSH session per host, running exec/view/create/edit/grep/glob with POSIX paths and shell state (cd, env) persisting across calls. Bypasses slow or flaky SMB/CIFS mounts entirely, giving native-speed file operations without drive letters or remounts.19,226 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to have persistent, fully interactive SSH sessions into remote hosts, behaving like a local terminal.14 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to maintain persistent SSH terminal sessions and transfer files to/from remote servers. Allows stateful command execution, natural language server management, and seamless file operations through SSH connections.10 npm35MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to run shell commands, read, write, edit, search, and stream files on remote SSH servers and Docker containers, including nested multi-layer chains, without installing any runtime on the target hosts. It auto-injects a self-contained Go helper with adaptive zstd compression for fast transfers and process control.9MIT
TDQS
Scored across 12 tools
Tools are largely distinct: remote_list (single dir), remote_find (recursive by name), remote_search (by content), and remote_stat (specific path properties) have clearly different scopes, and exec vs exec_bg vs job_check/list are well separated. There is mild overlap in the cluster of 'inspect the filesystem' tools, but descriptions disambiguate them adequately.
Every tool uses a consistent remote_ prefix followed by a clear verb or verb_noun suffix (remote_list, remote_read, remote_write, remote_exec_bg, remote_job_check). The pattern is predictable throughout with no convention mixing.
12 tools is well within scope for a remote file-and-exec server, and each tool covers a distinct operation (listing, searching, reading, writing, replacing, executing, background jobs, health). No redundancy or padding.
Core file lifecycle (read, write, replace) plus search, exec, and background-job management are covered, but there is no explicit delete, mkdir, or move/rename operation. These gaps are workaround-able via remote_exec shell commands, so they are minor rather than blocking.