Maccy + Cyberduck: A Clipboard Workflow That Actually Saves Time

Quick answer: Cyberduck moves files, but you spend the rest of the session shuffling text: remote paths, share URLs, hostnames, bucket names, and commands. Maccy keeps all of it in a searchable history, so you stop re-copying. Open it with ⇧⌘C, type a few letters, press Return, and the paste lands in the right field.

TL;DR

  • Use Maccy as a short-term memory for paths and URLs while Cyberduck handles the transfers.
  • Pin the strings you reuse daily (hostnames, deploy paths, bucket prefixes). Let everything else age out.
  • Never let credentials sit in history. Add your password manager to Maccy’s ignore list.
  • Pre-signed and temporary URLs expire. Don’t trust old entries.

You’re on the third deploy of the afternoon. You copied a remote path in Cyberduck, then a share link, then a hostname from a ticket, then an scp command from a README. Now you need the very first path again. Without a clipboard history, you go back and copy it a second time. With one, you press a shortcut and type three letters.

This guide covers what that looks like in practice. I’ll also say where the combination falls short, because it does.

What do Maccy and Cyberduck each do?

Maccy is a free, open-source, local-first clipboard manager for macOS. It keeps a history of what you copy, lets you search it by typing, and pastes the selected item into the frontmost app. Cyberduck is a free, open-source file browser for macOS and Windows that connects to servers and cloud storage over protocols such as SFTP, FTP, WebDAV, and Amazon S3.

They don’t integrate and don’t need to. Both work through the system pasteboard and the frontmost window, so any text Cyberduck puts on the clipboard, Maccy app can remember.

Where does Cyberduck put text on your clipboard?

Cyberduck produces a lot of short strings that you immediately want somewhere else. Menu names shift between versions, so check them against your own install.

What you copyTypical source in CyberduckWhere it usually goes
Remote file or folder URLEdit → Copy URLChat, ticket, config file, terminal
Remote pathInfo panel (⌘I) or the path barDeploy scripts, rsync and scp commands
Web or public URLInfo panel, Web URL fieldBrowser, CMS, email
Pre-signed S3 linkInfo panel or share optionsChat or email, usually time-limited
Hostname, bucket, prefixBookmark editor or connection dialogCLI tools, CI variables, docs

How do you build the workflow?

1. Copy freely, then retrieve by search

Don’t curate while you work. Copy the path, copy the link, move on. When you need something back, open Maccy mac and type a distinctive fragment such as releases or assets/img. Maccy clipboard‘s search narrows the list as you type, which beats scrolling by a wide margin. A distinctive substring is a better key than recency.

2. Pin what you reuse

Some strings come back every day: the production host, the uploads folder, the bucket prefix for a project. Pin those. In Maccy, pinning is done from the history menu (the default shortcut is ⌥P on the highlighted item ). Pinned items stay at the top and survive history clearing, so they work as lightweight snippets. They are not a substitute for a real snippet manager if you need templates with placeholders. Maccy doesn’t do that.

3. Use Go to Folder and Quick Connect as paste targets

Cyberduck has a Quick Connect field that accepts a full URL such as sftp://user@host/path . It also has a Go to Folder dialog for jumping to a remote path. Both are ideal targets for a Maccy paste: select the entry, press Return, and you’re there without clicking through directories. If your team shares paths in chat, copy once and pick it from Maccy whenever you need it.

4. Pair it with a terminal

Cyberduck is for browsing and transfers. For scripted work you’ll probably have a terminal open beside it. The same remote path you copy from Cyberduck gets pasted straight into an rsync or scp line. Maccy makes the round trip painless, because you can copy a path in Cyberduck, copy a command from your notes, and still get both back later.

5. Paste without formatting when pasting into chat or docs

Text copied from rich sources can drag formatting along. Maccy has a setting to paste without formatting . For paths and URLs, plain text is almost always what you want.

Is it safe to run a clipboard manager next to a file transfer client?

Yes, with one precaution: keep credentials out of clipboard history. Anything you copy ends up as a plain entry in Maccy’s history on your Mac, and Maccy stores that history locally rather than in the cloud. That’s good for privacy, but local still means readable by anything with access to your account.

  • Password managers: Many mark copied secrets with the standard “concealed” pasteboard type, and Maccy can skip those. Confirm this in Settings → Ignore , and add your password manager under ignored applications as a belt-and-braces measure.
  • Don’t copy passwords or keys by hand out of Cyberduck. It stores credentials in the macOS Keychain, so there’s rarely a reason to put one on the clipboard at all.
  • Treat pre-signed URLs as secrets. They grant access to an object until they expire. If one lingers in history, delete it from Maccy, or lower your history size so old entries drop off.
  • Clear history on shared machines when you finish a session.

What are the limits?

A few honest caveats before you rely on this.

  • Files aren’t text. Maccy is built around text, images, and similar clipboard content. Copying files between Finder and Cyberduck uses file references, and how those show up in Maccy history, if at all, depends on the source app . For file transfers, drag and drop or Cyberduck’s own upload dialog remains the reliable route.
  • Stale entries mislead. A path that was valid last week may point at a folder you’ve since renamed. A pre-signed link may have expired. Maccy can’t know.
  • It’s a memory aid, not automation. If you do the same transfer on a schedule, you want Cyberduck’s CLI companion, a script, or a sync tool. Check Cyberduck’s documentation for what’s current .

Quick-reference: a sample session

  1. Open the production bookmark in Cyberduck. The host is already pinned in Maccy for CLI use.
  2. Navigate to the release folder. Copy its URL.
  3. Switch to the terminal and run your sync using a path picked from Maccy.
  4. Back in Cyberduck, jump to a second folder with Go to Folder and a path from Maccy search.
  5. Copy the share link and paste it into the ticket. Then delete it from Maccy if it’s sensitive.

Is this worth setting up?

If you touch Cyberduck once a month, no. If you hop between servers, buckets, and tickets daily, the saving is real: not seconds per paste, but the avoided context switches of going back to re-copy something you already had. Maccy costs nothing, runs locally, and doesn’t care what app you’re in, so it’s a cheap experiment.

FAQ

Does Maccy work with Cyberduck?

Yes. Maccy records whatever lands on the macOS clipboard, so URLs and paths copied from Cyberduck appear in its history like any other text. There is no plugin or special setup.

Can Maccy store my Cyberduck passwords?

It shouldn’t. Cyberduck keeps credentials in the macOS Keychain. Avoid copying secrets by hand, and add your password manager to Maccy’s ignore list.

How do I keep frequently used paths handy?

Pin them in Maccy. Pinned items stay at the top of the list and aren’t removed when history is cleared.

Is Maccy’s clipboard history private?

Maccy is local-first, so history stays on your Mac. It is still readable on that machine, so ignore sensitive sources and clear history on shared computers.

Try it for one deploy day and see how often you open Maccy instead of re-copying. Which string in your own workflow gets copied the most?

If you want to try it yourself, maccy.at is a free, open-source clipboard manager for macOS — the clipboard history guide covers the rest.