Maccy on GitHub: Download, Build, and Use It

#What searching “maccy github” gets you

Maccy is a lightweight, open-source clipboard manager for macOS, and the repository at github.com/p0deje/Maccy is the canonical source for its code and its release builds. It is maintained by Alexey Rodionov, released under the MIT license, and written in Swift. When people type maccy github into a search box, they almost always want one of three things: the source to read or fork, a free binary to download, or the release notes for a version they already run. The repo covers all three.

The honest thing to say up front is that you do not strictly need GitHub to run Maccy. The app is also on the Mac App Store, and it installs in one command through Homebrew. But the GitHub repository is the origin. The App Store build and the Homebrew cask both trace back to what ships there, and the license that makes Maccy free to read and fork is the whole reason the app has the reputation it does. So if you found the repo, you found the real thing.

Prices and layout verified August 2026 against the repo and App Store listing; confirm details there, since a project like this moves.

#The three ways to install Maccy

All three land you on the same app. The difference is how you keep it updated and how much you trust each pipe.

1. A GitHub release DMG

Open the repo, click Releases in the right sidebar, and grab the latest .dmg from the top entry. Recent tags at the time of writing are in the 2.7 range, part of the Maccy 2 line that rewrote the app in SwiftUI. Mount the DMG, drag Maccy into Applications, launch it, and grant the Accessibility permission it asks for so it can read the clipboard. From then on the app updates itself in place through Sparkle, so you rarely revisit the releases page unless you want the changelog.

2. The Homebrew cask

If you already manage apps with Homebrew, this is the least friction:

# install
brew install --cask maccy

# later, upgrade it with everything else
brew upgrade --cask

The cask points at the same signed release, so you are not trading safety for convenience. You get the tidy benefit of one upgrade command that sweeps every cask on your machine at once.

3. The Mac App Store

The App Store listing costs $9.99. It is not a different or better app: it is the same Maccy, sandboxed to satisfy Apple’s rules, sold as a way to fund the work. If you want App Store update handling, receipts and a one-tap install, and you are happy to pay the developer directly, this is the clean choice. If you prefer free, the GitHub and Homebrew routes are fully legitimate and identical in features.

Whichever route you pick, the mechanics of copying and pasting on the Mac do not change; Maccy just remembers what you already do. If you are shaky on the basics, my walkthrough of how to copy on a Mac covers the keystrokes a clipboard manager sits on top of.

#Building Maccy from source

This is the part most “maccy github” searches are secretly after: not the binary, but the code. Because Maccy is Swift and MIT-licensed, you can clone it, open it in Xcode, and build a copy that is yours to change. The skeleton looks like this:

# clone the official repo
git clone https://github.com/p0deje/Maccy.git
cd Maccy

# open the project in Xcode
open Maccy.xcodeproj

From there you build and run with Cmd+R the same way you would any Xcode project. Two things trip people up. First, you need a current Xcode that matches the macOS SDK the project targets, so keep Xcode updated before you fight a build error that is really a version mismatch. Second, code signing: Xcode will want a signing team. For a build you only run yourself, an ad-hoc or personal-team signature is enough; you do not need a paid Apple Developer account just to compile it for your own machine.

Reading the source is worth an hour even if you never change a line. A clipboard manager holds everything you copy, passwords included when you are careless, so seeing exactly how a candidate app stores that history is the strongest trust signal there is. This is the same reasoning I apply to notch apps in whether Boring Notch is safe: open code you can read beats a closed binary you have to believe.

#What Maccy stores, and where

Once it is running, Maccy is deliberately small. It lives in the menu bar. The default shortcut, Shift+Command+C, pops a searchable list of your recent clipboard entries; you type a few characters, the match jumps to the top, you press Return and it pastes. That loop is the entire app, and its restraint is the point.

• Local only. Everything Maccy keeps is stored on your computer. There is no account and no sync server, which is exactly what you want from something that sees every copy you make.
• A deep but bounded history. It holds a large history, up to 999 items by default and configurable, and search stays instant regardless of how full it is.
• Pinning and ignore rules. You can pin entries you reuse constantly and tell it to skip apps like password managers so secrets never enter the history in the first place.

If you are weighing Maccy against the other well-known managers, that comparison deserves its own page rather than a paragraph here. I put the options side by side in the guide to clipboard managers on the Mac, looked at Maccy specifically in the Maccy clipboard manager write-up, and covered the polished paid alternative in the Paste clipboard manager review. The short read: Maccy wins on being free, open and fast, and it intentionally skips the heavier features some paid apps chase.

#Is downloading Maccy from GitHub safe?

Generally yes, with one rule: get it from the right place. There are forks and mirrors of Maccy on GitHub, some innocent, and a stranger’s fork is not something to install a compiled binary from. The safe pattern is simple.

• Trust one repo. Downloads and release notes should come from github.com/p0deje/Maccy or from the Homebrew cask that mirrors it. Treat any other download link with suspicion.
• Prefer the release, not a random build. The Releases page ships a signed DMG. A signature does not prove the app is flawless, but it proves the file was not tampered with after the developer built it.
• The source is your audit. The reason open-source clipboard tools earn trust is that the storage code is right there to read. You do not have to take my word or anyone’s; the answer is in the repo.

None of this is unique to Maccy. It is the same checklist for any Mac utility that wants deep permissions, and it is why I keep pointing people at code they can read rather than promises they have to trust.

#Where a notch tray fits, and where it does not

Mine to disclose: I build NotchBay, and its clipboard tray solves a slightly different problem than Maccy. Maccy is a menu-bar list you summon with a keystroke and dismiss. NotchBay keeps a tray inside the MacBook notch, sorted automatically by type: text, links, colors, images and files each get their own lane, and screenshots are run through OCR so text inside an image is searchable. Pinned clips stay forever; the rest holds the last 60. It is a smaller, always-in-your-eyeline surface rather than a deep archive.

That difference decides which one fits you. If you want a bottomless, keyboard-driven history that is free and open source, Maccy is the honest answer and you should just install it; nothing below changes that. NotchBay is worth a look only if you also want call controls, live activities and dictation living in the notch, with the clipboard as one tray among several rather than the whole app. NotchBay requires macOS 26 (Tahoe) and a MacBook with a notch, and it is not open source, so if auditable code is your bar, Maccy is the better fit and I will happily say so.

Two apps, two shapes of the same instinct: stop losing the thing you copied a minute ago. Maccy does it as a list. NotchBay does it as a tray in a strip of screen macOS otherwise ignores.

#Frequently asked questions