shipback-sftp
Related Servers
Alternatives to shipback-sftp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents and developers to perform secure, ultra-fast differential deployments over FTP, FTPS, and SFTP, inspect remote directory trees, test connectivity, and run dry-run diffs without exposing server credentials.2MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to manage website deployments over SFTP/FTPS by listing sites, testing connections, comparing files, previewing changes with approval tokens, creating SHA-256 verified backups, and executing authorized uploads.71MIT
- AlicenseNot gradedqualityDmaintenanceBridges AI coding assistants with website codebases, local git repositories, and shared hosting via FTP/SFTP, enabling code discovery, file management, git operations, smart deployments, backups, and rollbacks.10 npmMIT
- AlicenseAqualityAmaintenanceEnables AI agents to inspect and manage remote hosts over SSH with tiered blast-radius containment that classifies and blocks destructive commands, plus forensic post-flight assertions that verify ports, processes, files, and HTTP health. It also provides long-running background task envelopes and atomic SFTP file editing with automatic backups, unified diffs, and one-click rollback.12MIT
- AlicenseAqualityFmaintenanceAgent-native hosting: your agent deploys any folder to a live URL in one command — no account, no dashboard, no CAPTCHA — and hands the human a link plus a plain-language summary. Full deploy lifecycle as MCP tools (deploy, verify, logs, inspect, rollback), production approval human-only; static sites and full Node.js apps, open source (Apache-2.0).13Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA local MCP server that automates the deployment of static directories to remote hosts using rsync. It features support for interactive SSH authentication including MFA/OTP flows and provides tools to verify reachable URLs after deployment.8 npmApache 2.0
TDQS
Scored across 9 tools
Tools are clearly delineated: preview/deploy and preview/restore form explicit two-step pairs, while check_server_changes vs pull are complementary but distinct. No overlapping purposes or ambiguous boundaries.
Mostly action-oriented and consistent with list_*, preview_*, check_*, and bare verbs like deploy, pull, restore. 'history' is the lone noun, and mixing bare verbs with verb_noun is a minor deviation.
9 tools is well within the ideal range. Each maps to a distinct step in the deploy/pull/restore workflow with no filler or redundancy.
Core lifecycle is covered: list sites, preview/deploy, preview/restore, pull, check changes, and list backups. Gaps include no management of local backups created by pull and no add/edit/remove site operations (only list_sites).