Coolftp

coolFTP

Let Claude deploy your site to your SFTP or FTP host, with undo and a check that it is actually live. One line in Claude Code:

/plugin install coolftp --marketplace anivdel/coolFTP

Then say "set up coolFTP for this project" and "deploy this". Only files whose content changed go up, the git commit is recorded next to the deploy, the site is fetched afterward to prove it answers, and "undo that" puts the previous version back, no git needed. Works with any host that speaks SFTP or FTP: Hostinger, HostGator, Bluehost, GoDaddy, any cPanel box, your own VPS. Free for 1 site and MIT; Pro ($49 once) unlocks unlimited sites. Website: coolftp.com.

The plugin, the coolftp CLI and the MCP server run on macOS, Linux and Windows with Node 18 or newer, and Cursor, Codex or any agent with a shell can drive them too. The Windows desktop app is an optional companion: with it open, you watch every agent call live and click to approve deletes, undos and rollbacks.

With the desktop app open, agents ask before they delete anything:

Why

Every FTP client assumes a human is clicking. coolFTP assumes a human is watching and an agent is doing.

• Hash-based deploys. A manifest on the server records the SHA-256 of every deployed file. Timestamps lie; hashes do not.
• Undo, no git needed. Every deploy moves the files it overwrites or deletes into a backup folder on the server first. coolftp undo puts them back, even from a dirty tree.
• Deploy history with git. Each deploy stores the commit, branch, dirty flag, message, byte count, which agent ran it, and whether the site verified live.
• One-command rollback. coolftp rollback restores the previous live commit through a temporary git worktree.
• Verification. Give a site its public URL and every deploy fetches the changed pages, compares static files byte for byte with what you uploaded, and exits non-zero when the site does not answer. coolftp verify does the same on demand.
• Live agent feed and approval dialog, in the desktop app. Deletes, --delete deploys, rollbacks and undos wait for your click while the app is open. Deploys show as a progress card, and a Windows notification tells you how they ended.
• Safety by default. Pinned SSH host keys, passwords encrypted with your Windows account, a first-deploy guard that refuses to delete files it never uploaded, changed files swapped into place rather than overwritten, sizes confirmed by the server, resumable deploys.

packages/core   shared TypeScript library: transports, sites, hash manifest, sync, deploy
packages/cli    `coolftp` command line + `coolftp mcp` MCP server for agents
packages/app    Electron desktop app (two-pane browser, transfer queue, live agent feed)
site/           landing page for coolftp.com
scripts/        build + end-to-end test

Install

The CLI and the MCP server run anywhere Node 18 or newer does: Windows, macOS, Linux, a headless box, CI.

npm i -g coolftp
coolftp --version

No install at all: npx coolftp ... runs the same thing.

The desktop app is Windows for now: the installer, a portable .exe and the Claude Desktop extension (.mcpb) are on the download page with their SHA-256s.

Build from source

npm install
npm run build
npm run app          # opens the desktop app
node packages/cli/dist/coolftp.js --help

To get a global coolftp command from this checkout instead of npm: cd packages/cli && npm link.

Add a server

# SFTP with your existing ~/.ssh key or the ssh-agent
coolftp site add coolftp.com --host coolftp.com --user deploy --root /var/www/html

# FTPS with a password (shared hosts)
coolftp site add oldhost --host ftp.oldhost.net --user me --protocol ftps --password '...' --root /public_html

coolftp site test coolftp.com

Or use the Sites button in the app. Sites live in %USERPROFILE%\.coolftp\sites.json on Windows and ~/.config/coolftp/sites.json elsewhere. (Up to 0.1.4 the Windows folder was %APPDATA%\coolftp; the first run of a newer version copies it over. COOLFTP_HOME overrides the folder.) On Windows, passwords in that file are encrypted with DPAPI under your account; on macOS and Linux they are stored as-is until a keychain backend lands, so prefer keys for SFTP there.

Link a project and deploy

cd my-site
coolftp init coolftp.com --local-dir dist --build "npm run build"
coolftp diff                       # preview
coolftp deploy -m "first deploy"
coolftp deploy --delete            # also remove remote files deleted locally
coolftp deploy --commit -m "msg"   # git add -A, git commit, then deploy
coolftp undo                       # put the previous versions back
coolftp verify                     # re-run the live checks
coolftp history

Exit codes: 0 deployed (and verified, when the site has a URL), 1 something failed before or during the upload, 3 the files landed but the live checks did not pass. -q drops progress and per-file output and keeps the result line, warnings, errors and the checks. Deploys of more than 20 files print one progress line every few seconds instead of a line per file, and long plans are summarised by folder.

coolftp init writes .coolftp.json:

{ "site": "coolftp.com", "localDir": "dist", "build": "npm run build", "ignore": ["*.map"] }

Commit it. Add a .coolftpignore (gitignore syntax) for anything that must never go up. .git, node_modules, .env*, *.log and the coolFTP files are always excluded.

When a site's FTP root is not the web root (shared hosts often log you in one level above public_html), point the project at the right folder and tell coolFTP where it is served:

coolftp init myhost --remote-root /public_html --url https://example.com

Every command then works relative to that folder: coolftp push js/app.js js/app.js, coolftp ls, coolftp stat, coolftp cat, coolftp rm all resolve against /public_html, the same place deploy writes to. Paths starting with / are still absolute on the server. The url makes the changed-file URLs and the post-deploy check point at https://example.com/js/app.js rather than at the FTP path.

A push confirms the uploaded size with the server, reports any folder it had to create (with a warning when a single file opens a new top-level folder, which is what a stale public_html/ prefix looks like), and records a file pushed inside the project's remote directory in the deploy manifest, so the next deploy does not send it again.

Git Bash rewrites arguments that start with / into Windows paths before any program sees them. coolFTP undoes that when it recognises the Git install prefix and refuses anything else that looks like a drive path, so coolftp ls /public_html works from Git Bash too. If you hit the refusal, use a relative path or set MSYS_NO_PATHCONV=1.

Let Claude Code drive it

The coolFTP plugin is the one-step way: it starts the MCP server, teaches Claude how to deploy safely, adds /coolftp:setup, /coolftp:deploy, /coolftp:undo and /coolftp:live, and shows each deploy in a live panel beside the chat. In Claude Code:

/plugin install coolftp --marketplace anivdel/coolFTP

Answer y to add the marketplace, then pick a scope. In the Claude desktop app: + next to the prompt box, Plugins, Add marketplace anivdel/coolFTP, then add coolftp. It needs Node 18 or newer and nothing else; the desktop app is optional. Then say "set up coolFTP for this project". Details in plugins/coolftp.

The MCP server by hand

For other MCP clients, or to wire Claude Code yourself without the plugin. With the CLI installed from npm, on macOS and Linux:

claude mcp add --scope user coolftp -- coolftp mcp

On Windows, npm installs coolftp as a .cmd shim, so go through cmd:

claude mcp add --scope user coolftp -- cmd /c coolftp mcp

Without a global install: claude mcp add --scope user coolftp -- npx -y coolftp mcp (again behind cmd /c on Windows). --scope user registers it for every project on the machine; drop it to register for the current project only.

Cursor, Windsurf and other MCP clients take the same server in their mcp.json:

{ "mcpServers": { "coolftp": { "command": "coolftp", "args": ["mcp"] } } }

From a source checkout instead of npm, point at the built file:

claude mcp add coolftp -- node "C:\path\to\cool FTP\packages\cli\dist\coolftp.js" mcp

Tools exposed: coolftp_sites, coolftp_license, coolftp_status, coolftp_init, coolftp_diff, coolftp_deploy, coolftp_undo, coolftp_verify, coolftp_rollback, coolftp_history, coolftp_ls, coolftp_stat, coolftp_read, coolftp_write, coolftp_upload, coolftp_download, coolftp_mkdir, coolftp_delete, coolftp_rename. Results are summarised for an agent: counts and a folder breakdown instead of thousands of paths, a live verdict on every deploy, and the transfer log collapsed after 20 files. The server checks on every call whether the desktop app is running, so the app can be opened and closed during a session.

Use it from the Claude Desktop app

The same MCP server ships as a Claude Desktop extension. npm run mcpb packs it into release/coolFTP-<version>.mcpb (the download page carries the built one); open that file in Claude Desktop and hit Install. Claude gets the coolftp_* tools, and every call still routes through the desktop app while it is open, so deploys show up there and deletes, undos and rollbacks wait for your click. A chat has no working directory, so set Default project folder in the extension's settings or name the folder in the chat; a project's own .coolftp.json is found either way. The bundle is unsigned for now, which the install dialog points out.

server.json describes the server for the MCP Registry twice over: as the coolftp npm package (run with npx coolftp mcp) and as the .mcpb bundle. npm run mcpb keeps the versions and the bundle hash current. The release steps, npm publish included, are in docs/PUBLISHING.md.

Safety rails for agent-driven deploys

• Approval dialog. While the desktop app is open, an agent call that deletes a path, deploys with --delete, rolls back, or undoes a deploy pops a dialog in the app and waits for your click. No answer within two minutes is a deny. There is a checkbox to auto-approve for the rest of the session.
• First-deploy delete guard. Before a manifest exists on the server, --delete is refused if the target folder contains files coolFTP never uploaded. Pass --delete-untracked to override.
• Undo. Before a deploy overwrites or deletes a file, the live copy is renamed into .coolftp/backup/<deployId>/ on the server, so nothing extra is transferred. coolftp undo restores those versions, removes the files that deploy added, and is itself undoable; --dry-run shows the work first, --to <deployId> reverts an older deploy when nothing later touched its files. The last five deploys keep their backups (coolftp init --keep-backups <n>, 0 to turn it off). The Deploys tab has an Undo button.
• Rollback. coolftp rollback restores the previous commit that was live for the project, using a temporary git worktree so your working tree is untouched. --to <commit|deployId> targets any point in history. The Deploys tab in the app has the same buttons.
• Verification. Give a site a public --url (or a project one with coolftp init --url) and every deploy prints the URLs of changed files, fetches the homepage and up to four pages and reports the status codes, and compares up to four static files byte for byte with the local copy. A status failure exits with code 3; a byte mismatch is reported as stale (something between the server and the world, a cache or a CDN, is still serving the old version) without failing. coolftp verify re-runs the checks any time; history shows live, failed or stale per deploy. MCP results carry the same verdict so an agent never calls an unverified deploy live.
• Confirmed uploads. In jobs of up to 50 files, every upload's size is read back from the server and a mismatch is retried. Changed files upload beside the live copy and are swapped in with a rename, and the manifest is written the same way, so a dropped connection never leaves a half-written file or manifest behind.
• Host key pinning. SFTP host keys are recorded on first use in known_hosts.json and a changed key is refused with a loud error. coolftp site trust <name> forgets the recorded key after a legitimate server rebuild; coolftp site keys lists them.

Any agent with a shell can simply run coolftp deploy inside a linked project. The CLI detects Claude Code, Cursor, Codex, Gemini CLI and Aider from their environment and labels the call accordingly; pass --agent <name> to override.

The deploy skill Claude follows ships in the plugin, in plugins/coolftp/skills/deploy.

How agent calls reach the app

When the desktop app is running it listens on a random 127.0.0.1 port and writes hub.json in that same folder with the port and a per-session token. The CLI and MCP server look for that file, and if the app answers, they send the command to the app instead of running it themselves. Events stream back as NDJSON, so the terminal still shows progress, and the app shows the same call in its Agents panel, its transfer queue, and its deploy history. If the app is closed, the CLI runs everything in-process. --direct forces that.

How deploys decide what to upload

1. Scan the local folder, hashing files (SHA-256, cached by size and mtime).
2. Read <remoteRoot>/.coolftp/manifest.json from the server. It maps every deployed path to its hash.
3. Upload files whose hash differs or which are missing from the manifest, over up to four FTP connections for jobs of eight files or more (coolftp site add --connections <n> changes the count; SFTP multiplexes one). A changed file is uploaded beside the live one, the live one is moved into the backup folder, and the new one is renamed into place. Files in the manifest but not local are reported as stale and only removed with --delete, which also moves them into the backup.
4. Write the new manifest (to a temporary name, then swapped in), plus a deploy record (git commit, branch, dirty flag, message, agent, counts, duration, backup, connections), prune backups beyond the kept count, then run the live checks and store the verdict with the record.

On a server with no manifest yet, the remote tree is walked and compared by size; that first deploy establishes the manifest. --force re-uploads everything.

The manifest directory gets a .htaccess with Require all denied. On nginx, deny /.coolftp yourself or point remoteRoot above the web root.

Tests

npm run e2e

Starts a local FTP server (ftp-srv) and a local SFTP server (ssh2, in scripts/lib/sftp-server.cjs) in temp directories and drives the CLI through site setup, init, the first-deploy delete guard, deploy, manifest diff, delete sync, --commit, undo and redo from the server-side backup, backup pruning, rollback by previous commit and by deploy id, push (size confirmation, created-folder warning, manifest recording), pull, stat, rename, mkdir, remove, a 30-file deploy over four FTP connections, verification against a local web server (a passing deploy, a stale copy, an unreachable site with exit code 3, quiet mode), history, encrypted passwords, SSH host key pinning (a swapped server key is refused, then trusted), and the MCP server driven over stdio. 190 checks in total.

Try it without a real host

npm run dev:ftp     # ftp://demo:[email protected]:2121, remote root /public_html
npm run dev:sftp    # sftp://demo:[email protected]:2222, remote root /public_html

Both seed a temp folder with a few files. Add a site pointing at one, connect in the app, and deploy any folder at it.

Free and Pro

All of the code is MIT. coolFTP Free has every feature for one site. coolFTP Pro is a one-time $49 payment for unlimited sites, with updates for life and priority support, sold at coolftp.com.

Keys are CFP1.<payload>.<signature>, Ed25519-signed, verified offline against the public key in packages/core/src/license-pubkey.ts. A genuine key unlocks Pro in every build. Keys are issued with updatesUntil 9999-12-31 so they also work in older builds, which still check that date.

• node scripts/license/keygen.cjs creates the signing key pair once. The private half lives in scripts/license/private/ (git-ignored). Back it up; losing it invalidates every key ever issued.
• node scripts/license/issue.cjs --email [email protected] issues a key by hand.
• npm run test:license exercises activation, tampering, expiry, and removal through the CLI.
• coolftp license, coolftp license activate <key>, coolftp license remove, or the Pro button in the app.

Purchases run through Stripe Checkout. site/api/stripe-webhook.php receives checkout.session.completed, signs a key with the libsodium copy of the private key, stores a record outside the web root, and emails the key from [email protected]. site/api/resend.php re-sends a key for an email address, rate limited. Real values go in site/api/config.php, which is git-ignored; config.example.php shows the shape.

Package the app

npm run dist

Uses electron-builder with packages/app/electron-builder.yml. Output lands in release/. Builds are unsigned.