Coffee Port vs Raycast Port Manager
The best tool there is for killing whatever has 3000 right now. Its names live on the ports it can see, so a project that is not running has nothing to attach one to.
Remembers it only while it is running
What it remembers
Its Named Ports command assigns labels to ports so they are easier to identify in the list. The list itself is the set of TCP listeners on this machine, so a label is something you read when the thing is already running.
Sources: Port Manager in the Raycast Store. Checked .
What Coffee Port cannot do
It cannot see what is running. A web page has no way to list the sockets on your machine, and the way to get one — a daemon on localhost for the browser to talk to — would mean opening up the policy that stops a compromised page sending your decrypted ledger somewhere else. That is not a trade worth making for a list of process ids you can already get in a second.
So these are not rivals. Raycast Port Manager answers what is on 3000 right now; this answers what 3000 is for. Most people who want the second one already have the first.
Point by point
| Point of comparison | Raycast Port Manager | Coffee Port |
|---|---|---|
| What is listening right now | Every TCP listener, in the launcher or the menu bar, refreshed as it changes — plus the process behind each one and a key to kill it. | Nothing. A web page cannot see what is bound to a port, and this one does not pretend to — pair it with any of the tools on this page for that half. |
| What it shows | TCP listeners, their ports, and the process behind each one — in Raycast or in the macOS menu bar. | Every port you have claimed, running or not. |
| Naming a port | Yes. Named Ports attaches a memorable label to a port in the list. | A label, a project, a service kind, notes and any custom field you invent — on the port, not on the number. |
| A port nothing is bound to | Not in the list, so there is nothing to name or read. | A ledger. A port stays in it whether or not anything is bound to it, so 4012 still says which project claimed it and why after three months of not being run. |
| Killing a process | Yes — SIGTERM or SIGKILL, from the launcher, in about two seconds. | No. It is a ledger, not a process manager. |
| Choosing a new port | Yours to pick. | Hands out the next free number by rule — 40xx for personal things, 41xx for client work, or whatever you write — and says which rule chose it. |
| Where it runs | Raycast, on macOS and Windows. | Any modern browser |
Which to use
Use Raycast Port Manager when
- Something has 3000 and you want it dead in two keystrokes. Nothing here competes with that.
- You live in Raycast and want the answer without a browser tab.
- You want the open-port list in your menu bar all day.
- You are on one machine and the labels only have to make sense to you.
Use Coffee Port when
- You want the record to survive the process exiting — and the laptop being replaced.
- You want the number handed out by a rule rather than picked by hand.
- You want to know why 4012 is spoken for when nothing is on it.
- You want the same ledger on the desktop and the laptop, without either of them holding it in the clear.
Questions
- Does Raycast Port Manager remember port names?
- It has a Named Ports command that attaches labels to ports so you can recognise them in the open-port list. The list is what is listening now, so a name is something you see while the process is up rather than a record of what the port is reserved for.
- Can I use Raycast Port Manager and a port ledger together?
- That is the pairing we would suggest. Raycast is for “kill whatever has this port”; the ledger is for “what is this port, and which one should I use next”.
- Is Raycast Port Manager free?
- It is a free extension in the Raycast Store. Raycast itself has a free tier and paid plans for teams and Raycast AI.