Skip to content Black FridayUp to 76% off Vitals, Levers and SoundBar, until 5 December
Vitals · Dev servers and ports

Find what is using a port on your Mac, by project

The Developer tab shows what is running by the project folder it was started from, and every port in use with the process that holds it and whether your network can reach it. A dev server left idle for days is pointed out, with what stopping it would free.

The Vitals Developer tab on Projects: 11 projects running, a banner saying 4 dev servers are idle with Stop All, and each project with its ports, state and memory

Projects: grouped by folder, not by command

Every project leaves things running: a dev server from Tuesday, a local database, a test watcher in a closed tab. In Activity Monitor they are rows called node and python, with no port shown.

Vitals groups processes by the folder they were started from. Three things called node become storefront, api and docs. Each project is one row with the app that started it, such as Terminal, Cursor or Claude, its memory and CPU, and every port it listens on. Containers started by docker compose from the folder sit under the same project.

Open a row to see each process in the project. When a second project fails to start because port 3000 is taken, or the Mac is warm for no reason you can name, this is the list that explains it.

Ports: what is on 3000, without a terminal

The Ports section lists every listening port on the Mac, sorted by whose it is: your projects first, then idle dev servers, containers, Homebrew services, and other apps and macOS. The system’s own ports are named in plain words, such as AirPlay Receiver on 5000 and 7000.

Press ⌘F and type a number, and the process holding that port is named with its project. Each row has Open in Browser and Quit, and says how long the process has been running. When a port is “already in use”, this is where you find the earlier server that still has it.

A search for 3000 in Ports: port 3000 held by next dev in storefront, marked Yours with Stop, beside a container’s port and one of the system’s

Which ports your network can reach

Each port says who can connect: only this Mac, or other devices on your network. The ones open to the network are counted at the top and marked, so a dev server listening on every address is easy to spot. An iPhone connected by cable is told apart from the network.

32 ports in use with 4 open to your network: each port marked Network or This Mac, including macOS’s AirPlay Receiver on 5000 and 7000

Idle servers, and stopping them

A dev server that has done nothing for days carries a note saying how long, with an offer to stop it and what that frees: the memory and the port. Stop one, use Stop All, or quit a whole project so every process in it closes. Force Quit is there for one that will not answer.

Vitals never stops a server by itself. It asks first and says what will close.

The menu bar dropdown has the same Developer tab, with Projects, Ports and Containers. An idle server there carries a moon and how long, and ports open to your network come first. Over MCP, an assistant can ask what is on a port or which projects have a dev server going.

How to use it

  1. 1

    Open the Developer tab

    Projects is the first section. Each row is a project named after its folder, with its memory, CPU and ports.

  2. 2

    Find a port

    Choose Ports, press ⌘F and type the number. The process holding it is named, with its project.

  3. 3

    Check who can connect

    Each port says whether only this Mac or other devices on your network can reach it. The count of open ports is at the top.

  4. 4

    Stop a forgotten server

    An idle server says how long it has done nothing. Stop it, or quit its project. Vitals asks first.

The details

A project is
The folder a process was started from
Ports listed
Every listening port, grouped by projects, idle dev servers, containers, Homebrew services, other apps and macOS
Reach
Only this Mac, or other devices on your network
On each port row
Open in Browser, Quit, and how long it has been running
Stopping
Stop one, Stop All, or quit a project, after a confirmation
In Terminal
vitals ports and vitals projects

Questions

Why does my port say it is already in use?

Another process is listening on it, usually a server from an earlier session. The Ports section names it with its project and offers to quit it.

Can other devices on my network reach my dev server?

The Ports section says so for every port: only this Mac, or other devices on your network. Ports open to the network are counted at the top.

Will Vitals stop a dev server by itself?

No. It points out servers that have been idle for days and offers to stop them. Nothing stops until you confirm.

Does it show ports held by other apps and by macOS?

Yes. Every listening port is listed, and the system’s are named in plain words, such as AirPlay Receiver on 5000 and 7000.

Can I quit a whole project at once?

Yes. Quit the project and every process in it closes, after a confirmation.

The same feature on the app's own site: vitalsmac.com/features/dev-servers-and-ports

Find the app behind every number.