A
aldohushi1-stack/shipback-sftp
Deploy to cPanel. Undo in one command.
SECURITY.md ✓
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
- 复制上面的命令
- 粘成
claude_desktop_config.json里mcpServers的一项（本地服务器用 command + args，示例见 客户端接法） - 重启客户端
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"aldohushi1-stack-shipback-sftp": {
"command": "npx",
"args": ["-p", "shipback-sftp", "shipback"]
}
}
}解析自我们于 2026-10-26 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"aldohushi1-stack-shipback-sftp": {
"command": "npx",
"args": ["-p", "shipback-sftp", "shipback"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio aldohushi1-stack-shipback-sftp -- npx -p shipback-sftp shipback
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 1 ★ · aldohushi1-stack/shipback-sftp · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-10-23 · 最近见到 2026-11-14 · 共见到 26 次 · 被 23 个来源列出
- 评分构成
- 综合分 2,300 · 1 ★ · 23 个来源 · mcp
- 安装
npx -p shipback-sftp shipback
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
npx -p shipback-sftp shipback。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
aldohushi1-stack/shipback-sftp；我们收录于 2026-10-23；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# 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.
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/aldohushi1-stack-shipback-sftp/)
- 来源
- awesome · https://github.com/aldohushi1-stack/shipback-sftp
- 按领域浏览
- MCP 服务
- Traction
- 1 ★
- 收录来源
- 23 个独立来源
- 收录于
- 今天
- 安全策略
- 该仓库根目录有
SECURITY.md（我们只核文件存在，未核内容）
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。