# Your dev servers and open ports, by project.

Canonical page: https://vitalsmac.com/features/dev-servers-and-ports

Vitals shows what is running on your Mac by the project it came from, and every port in use with what holds it and who can reach it. The dev server you forgot on Tuesday is pointed out, with what stopping it frees. Nothing stops until you say so.

## Projects: Grouped by the folder it runs in, not by the command.

Three things called node become storefront, api and docs. Everything started from a project folder is one row, named after the folder, with the app that started it, its memory and CPU, and every port it listens on.

- One row per project, named after its folder
- The app that started it: Terminal, Cursor, Claude
- Memory and CPU for the whole project
- Compose containers under their project too

## Ports: What is on port 3000, without a terminal.

Ports lists every port in use on the Mac, sorted by whose it is: your projects, idle dev servers, containers, Homebrew services, then other apps and macOS. Press ⌘F, type 3000, and the process holding it is named, with Quit beside it. No lsof, no kill.

- Every listening port, grouped by whose it is
- ⌘F a number and it is found
- Open in Browser, or Quit, on each row
- How long each has been running

## Network: 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, so a dev server that anyone on a café's Wi-Fi could reach is easy to spot.

- Only this Mac, or open to the network
- Open ports counted at the top
- macOS's own named: AirPlay Receiver, Screen Sharing
- An iPhone on a cable told apart from the network

## Idle: The server you forgot, pointed out with how long.

A dev server that has done nothing for days carries a note saying how long, and an offer to stop it with what that frees: the memory and the port. Stop one, stop them all, or quit a whole project. Vitals asks first.

- Idle for days, pointed out
- What stopping frees: memory and ports
- Stop one, or Stop All
- Quit a whole project at once

## Dropdown: Check a project or a port from the menu bar.

The dropdown has the same Developer tab, with Projects, Ports and Containers. An idle dev server carries a moon and how long, the ports open to your network come first, and a click opens the window on that section.

- Projects, Ports and Containers in the dropdown
- A moon on an idle server, with how long
- Ports open to your network come first
- A click opens it in the window

## Why it matters: dev servers and ports on a Mac

Every project leaves things running. A dev server from Tuesday, a database you forgot was local, a test watcher in a tab you closed. In Activity Monitor they are a dozen rows called node and python, and the port each one holds is not shown at all; for that you open a terminal, type lsof -i :3000, and kill a number.

So the second project on port 3000 fails to start, the Mac is warm for no reason you can name, and the fix is a guess.

Vitals' Developer tab answers both. Projects groups what is running by the folder it runs in, with the memory, CPU and ports of each. Ports lists every port in use, with what holds it and whether your network can reach it. The dev server that has done nothing for days is pointed out and offered to stop, and Vitals asks before anything closes.

## How to use it

1. **Open the Developer tab.** Projects is its first section: one row per project, named after its folder, with its memory, CPU and ports. Open a row to see each process.
2. **Find what is on a port.** Choose Ports, press ⌘F and type the number. The process holding it is named, with its project.
3. **Check what your network can reach.** Each port says whether only this Mac can connect or other devices can. The number open to your network is at the top.
4. **Stop the forgotten one.** An idle server says how long it has done nothing. Stop it, quit its whole project, or Force Quit one process that will not answer. Vitals asks first and says what will close.
5. **Ask from your assistant.** Over MCP: what is on port 8080, which projects have a dev server going. For a project folder you trust, safe requests can be quit without asking; add the folder in Settings → Integrations.

## Compared with Activity Monitor

| | Activity Monitor | Vitals |
| --- | --- | --- |
| By project | No | Grouped by the folder they run in |
| Ports | Not shown; lsof in Terminal | Every port in use, beside the process that holds it |
| Who can connect | Not shown | Only this Mac, or open to your network |
| Idle servers | Nothing | Pointed out, with how long |
| Stopping | kill by number | Stop, or quit the whole project, after a confirmation |
| Containers | Processes only | Compose containers under their project |

## The words behind it

- [Listening port](https://vitalsmac.com/glossary/listening-port): A listening port is a network port where a process is waiting for incoming connections, such as a web server on port 3000.
- [PID](https://vitalsmac.com/glossary/pid): A PID, or process ID, is a number macOS assigns to each running process to identify it.
- [Zombie process](https://vitalsmac.com/glossary/zombie-process): A zombie process is a process that has finished running but still has an entry in the process table, because its parent process has not yet collected its exit status.
- [Force Quit](https://vitalsmac.com/glossary/force-quit): Force Quit ends an app or process immediately, without letting it save or clean up.
- [launchd](https://vitalsmac.com/glossary/launchd): launchd is the first process macOS starts at boot, with process ID 1.

## Questions

### How does Vitals know which project a process belongs to?

By the folder it was started from. Processes started from the same project folder are grouped under it, with the folder's name.

### Will Vitals stop a dev server by itself?

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

### Does it show ports held by apps that are not mine?

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

### Can other devices on my network reach my dev server?

The Ports section says so for every port: only this Mac can connect, or other devices on your network can. Ports open to the network are counted at the top and marked, so a server listening on every address is easy to spot.

### Does it work with Docker?

Yes. Containers are a section of the same Developer tab, with their ports. A container started by docker compose from a project folder shows under that project too, and its published ports are in the Ports section.

### What counts as a project?

The folder a process was started from. Everything started from the same folder is one project, named after it.

### Can I quit a whole project at once?

Yes. Quit the project and every process in it closes, after a confirmation. Force Quit is there for one that will not answer.

### 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 the project it belongs to, and offers to quit it.

## Read on

- [Claude Code using too much memory or CPU on a Mac? How to find it, and get it back](https://vitalsmac.com/claude-code-memory-usage-mac)
- [How to stop Docker containers on a Mac, one or all of them](https://vitalsmac.com/stop-docker-containers-mac)
- [Why is my Mac so slow? How to find the cause, and fix it](https://vitalsmac.com/why-is-my-mac-so-slow)
- [Vitals vs Activity Monitor](https://vitalsmac.com/vs/activity-monitor)
- [Vitals vs ProcXray](https://vitalsmac.com/vs/procxray)

## More of Vitals

Every feature is at [vitalsmac.com/features](https://vitalsmac.com/features). Vitals is paid once, with a year of updates or every update for life: [pricing](https://vitalsmac.com/pricing).
