A
aldohushi1-stack/shipback-sftp
Deploy to cPanel. Undo in one command.
SECURITY.md ✓
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Client config (built from the install command this repo gives)
{
"mcpServers": {
"aldohushi1-stack-shipback-sftp": {
"command": "npx",
"args": ["-p", "shipback-sftp", "shipback"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"aldohushi1-stack-shipback-sftp": {
"command": "npx",
"args": ["-p", "shipback-sftp", "shipback"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio aldohushi1-stack-shipback-sftp -- npx -p shipback-sftp shipback
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 1 ★ · aldohushi1-stack/shipback-sftp · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 23 sources
- Score
- score 2,300 · 1 ★ · 23 sources · mcp
- Install
npx -p shipback-sftp shipback
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx -p shipback-sftp shipback. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
aldohushi1-stack/shipback-sftp；first catalogued 2026-10-23；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# Shipback SFTP
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
SFTP deploys you can take back.
It's late, and the agent says "Deployed ✓". Then the client's contact form is gone. The agent overwrote a
file someone had fixed by hand in cPanel last week, and shared hosting has no git revert.
Shipback deploys a folder to any SFTP host: cPanel, Plesk, DirectAdmin, a plain VPS. Every deploy
can be undone with one command. You can run it yourself, script it, or hand it to Claude Code, Cursor or
any MCP client.
The undo promise: one command puts the site back byte for byte, even after a deploy that
was cut off halfway. It never overwrites a live edit. Each of the thirteen lines in the promise has its own test, and
if undo ever breaks one of them, that's the first bug I fix.
Backup before every overwrite. The server's copy of each file a deploy replaces is saved into
backup- / on the server, before the upload starts.
Never half a file. Each file goes up beside the live one and is swapped in whole, so a dropped connection
leaves the old file, not a broken one.
One-command undo. --restore puts those files back and removes the files that deploy added.
It won't undo over a live edit. If someone changed a file on the server after the deploy, restore
stops and names the file. Nothing is touched unless you pass --force, and even then the edited copy is
backed up first.
Restores can be undone too. A restore backs up what it replaces, the same way a deploy does.
One run at a time. A deploy or restore holds a lock on the site while it writes. A second one is turned away
with nothing changed, so an agent and a person can't deploy over each other.
Stays inside the site. Deploy and undo won't write through a symlink or over a special file on the server,
so a symlinked folder can't carry a write somewhere else.
Safe for agents. The MCP server has no switch to delete server files or skip the backup. A deploy
only runs the exact plan the agent previewed: if a file changed in between, it refuses.
Spots the drift. --pull --dry-run shows what changed on the server since your last deploy, so
edits made live in cPanel don't get overwritten by accident.
No git or SSH shell is needed on the server, just SFTP. It needs Node 18+. The tests run on Windows, macOS
and Linux with Node 18, 20 and 22 on every push. Passwords are kept in the OS keychain and never
pass through the model.
It has run in production. The deploy engine underneath has shipped aldo.today 235 times
since September 2026 (2,907 files to a cPanel host). Restore and the MCP server are new since 0.1, and the
cut-off handling behind the promise is new in 0.2.
## Quick start
bash
npm install -g shipback-sftp # installs the shipback and shipback-mcp commands
cd ~/sites # any folder with a sites.json in it (format below)
shipback mysite --dry-run # see the plan; asks for the password once and stores it
shipback mysite # deploy
shipback mysite --restore # changed your mind? undo it
No global install? npx -p shipback-sftp shipback mysite --dry-run works the same way. --sites
points at a sites.json in another folder.
From source: git clone https://github.com/aldohushi1-stack/shipback-sftp.git, npm install, then
node bin/cli.js wherever these docs say shipback.
It's late, and the agent says "Deployed ✓". Then the client's contact form is gone. The agent overwrote a
file someone had fixed by hand in cPanel last week, and shared hosting has no git revert.
Shipback deploys a folder to any SFTP host: cPanel, Plesk, DirectAdmin, a plain VPS. Every deploy
can be undone with one command. You can run it yourself, script it, or hand it to Claude Code, Cursor or
any MCP client.
The undo promise: one command puts the site back byte for byte, even after a deploy that
was cut off halfway. It never overwrites a live edit. Each of the thirteen lines in the promise has its own test, and
if undo ever breaks one of them, that's the first bug I fix.
Backup before every overwrite. The server's copy of each file a deploy replaces is saved into
backup- / on the server, before the upload starts.
Never half a file. Each file goes up beside the live one and is swapped in whole, so a dropped connection
leaves the old file, not a broken one.
One-command undo. --restore puts those files back and removes the files that deploy added.
It won't undo over a live edit. If someone changed a file on the server after the deploy, restore
stops and names the file. Nothing is touched unless you pass --force, and even then the edited copy is
backed up first.
Restores can be undone too. A restore backs up what it replaces, the same way a deploy does.
One run at a time. A deploy or restore holds a lock on the site while it writes. A second one is turned away
with nothing changed, so an agent and a person can't deploy over each other.
Stays inside the site. Deploy and undo won't write through a symlink or over a special file on the server,
so a symlinked folder can't carry a write somewhere else.
Safe for agents. The MCP server has no switch to delete server files or skip the backup. A deploy
only runs the exact plan the agent previewed: if a file changed in between, it refuses.
Spots the drift. --pull --dry-run shows what changed on the server since your last deploy, so
edits made live in cPanel don't get overwritten by accident.
No git or SSH shell is needed on the server, just SFTP. It needs Node 18+. The tests run on Windows, macOS
and Linux with Node 18, 20 and 22 on every push. Passwords are kept in the OS keychain and never
pass through the model.
It has run in production. The deploy engine underneath has shipped aldo.today 235 times
since September 2026 (2,907 files to a cPanel host). Restore and the MCP server are new since 0.1, and the
cut-off handling behind the promise is new in 0.2.
## Quick start
bash
npm install -g shipback-sftp # installs the shipback and shipback-mcp commands
cd ~/sites # any folder with a sites.json in it (format below)
shipback mysite --dry-run # see the plan; asks for the password once and stores it
shipback mysite # deploy
shipback mysite --restore # changed your mind? undo it
No global install? npx -p shipback-sftp shipback mysite --dry-run works the same way. --sites
points at a sites.json in another folder.
From source: git clone https://github.com/aldohushi1-stack/shipback-sftp.git, npm install, then
node bin/cli.js wherever these docs say shipback.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/aldohushi1-stack-shipback-sftp/)
- Source
- awesome · https://github.com/aldohushi1-stack/shipback-sftp
- Browse by field
- MCP servers
- Traction
- 1 ★
- Listed by
- 23 independent sources
- added
- today
- Security policy
- the repository has
SECURITY.mdat its root (we checked that the file exists, not what it says)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.