Let your assistant ask Vitals instead of guessing.

Claude, Claude Code, Codex, Cursor and any assistant that speaks MCP can ask Vitals what is running, which app is behind a number, what is on a port, and what the last month looked like. It gets real measurements instead of a process list, and it cannot quit anything without asking you.

Get Vitals for $15 All features
Ask AI ChatGPT Claude Perplexity AI Mode Grok Markdown
Codex Connected to Vitals
Claude Connected to Vitals
Cursor Connected to Vitals
My Mac feels slow. What is going on?
Asked Vitals
Google Chrome 48% CPU for 10 min · 3.3 GB
Xcode building · 6 cores
storefront-web node · 458 MB · unused for 3 days

Xcode is your build. Shall I ask Vitals to quit the dev server?

Yes
Vitals
Codex asks to quit storefront-web
node · port 4322 · 458 MB
Vitals thinks this is safe to quit.
Don’t Quit Quit

Done. 458 MB and port 4322 are free.

My battery is at 40% and it is not even noon. Why?
Asked Vitals
Zoom 11 W on average this morning
Google Chrome 4 W on average
Xcode 2 W, one build

Zoom used the most, through your call at ten. Chrome is next, with 42 tabs open. Nothing here needs quitting.

Something is on port 3000. What is it?
Asked Vitals
billing-api node · port 3000 · 204 MB

A dev server in billing-api, started two days ago and idle for three hours. It still answers, so it is yours to keep or quit.

Leave it.

Left running.

The numbers are simulated: a web page cannot read your Mac, and should not.

01Setup

One click per assistant, and it is on.

Claude, Claude Code, Codex and Cursor each have an Add button in Settings → Integrations that puts Vitals in the assistant's own list of tools. Any other assistant that speaks MCP takes the command shown there. Nothing is on until you add it.

  • Add for Claude, Claude Code, Codex and Cursor
  • A command for any other assistant that speaks MCP
  • Switches for what every assistant may see
  • Project folders by name only, if you prefer
General
Customize
Layout
Insights
Integrations
License
Let AI Assistants Ask Vitals
ClaudeAdded
Claude CodeAdd
CodexAdd
CursorAdd
Any other assistantCopy command
Assistants may see
System figures
Apps
Projects
History
Project folders by name only
One click per assistant What every assistant may see
02Questions

It gets the same numbers you see, with when they were measured.

Left to itself, an assistant runs ps and guesses. Through Vitals it gets the picture you have: apps with their helpers added up, projects with their ports, sessions with what they started, and every answer stamped with when it was taken.

  • What is using the CPU, memory, battery, disk or network
  • Which app a number belongs to
  • What is on a port, and whose it is
  • Which coding sessions are running, and what the last month looked like
Why is my Mac slow right now?
Claudeasked Vitals · 14:02
Chrome is behind it: 142% of a core for the last six minutes, 21.2 GB across 96 processes, most of it in one tab, github.com. The Mac is at 94% CPU and memory is fine.
Google ChromeRenderer · github.com1.84 GB · 61%
Want me to ask Vitals to quit that tab's process?
The app behind the figure When it was measured
03Quitting

It asks Vitals, and Vitals asks you.

An assistant cannot quit anything on its own. The request comes to you in a window of its own: what is asking, what it wants to quit, what is connected to it right now, and whether Vitals thinks it looks safe. You click, or you don't.

  • What is asking, and what it wants to quit
  • What is connected to it right now
  • Whether Vitals thinks it looks safe
  • In folders you trust, safe requests can go through without asking
Codex asks
Quit api (uvicorn)?
In ~/Projects/api, idle for 3 days.
Connected right nowNothing
Vitals thinksLooks safe
Don’t quitQuit
What is asking, and for what Nothing quits without you
04Privacy

Honest about what the assistant hears.

Vitals itself sends nothing anywhere. What it tells an assistant goes wherever that assistant sends its conversations, and app names, project folders and ports are in there. You turn it on knowing that, and you choose what it may see.

  • Vitals sends nothing anywhere
  • App names, project folders and ports are in the answers
  • Every tool but quit is read-only
  • Off until you turn it on
Vitals, on your MacMeasures, and answers when askedSends nothing anywhere
The answer: app names, project folders, ports
Your assistantClaude Code, Codex, Cursor, any that speaks MCPEvery tool but quit is read-only
Wherever that assistant sends its conversations
Its maker's serversWhere the assistant was going anyway
Off until you turn it on
Why it matters

MCP server, before and after

Ask an assistant why your Mac is slow and it runs ps aux, gets a thousand lines, and guesses. It sees node at 180% and cannot tell which project, which chat, or whether that is the test run you started on purpose. It sees a port in use and offers to kill whatever holds it.

Assistants are good at the next step, what to do about it. What they lack is the picture Vitals already has: apps with their helpers added up, projects with their ports, sessions with what they started, and what the last month looked like.

Vitals is an MCP server. Claude, Claude Code, Codex, Cursor and any assistant that speaks MCP can ask it what is running and get the same numbers you see, each with when it was measured. When an assistant wants something quit, it has to ask Vitals, and Vitals asks you, in a window of its own, with what is connected to it right now. You decide what it may see: system readings, apps, projects and history each have a switch, and project folders can go by name only.

How to use it

Where it is in Vitals

The tab, the menu bar item and the setting, in the order you would reach for them.

  1. 01

    Turn it on

    Settings → Integrations lists Claude, Claude Code, Codex and Cursor with an Add button each. Add puts Vitals in the assistant's own list of tools; an assistant that is open sees it when it next starts. Any other assistant that speaks MCP takes the command shown there.

  2. 02

    Choose what it may see

    Switch off system readings, apps, projects or history for every assistant at once, and give project folders by name only, so an assistant hears "shop" and not where that folder lives on your Mac.

  3. 03

    Ask

    What is eating my memory. What is on port 8080. Which coding sessions are running, and which chat is each. How hard was the Mac pushed this week, and when was it at a limit. Every answer says when it was measured.

  4. 04

    When it wants to quit something

    The request comes to you in a window of its own: what is asking, what it wants to quit, whether that looks safe, and what is connected to it right now. Nothing closes until you say so. For a project folder you trust, add it in Settings → Integrations and safe requests there go through without asking.

Compared

MCP server: Activity Monitor and Vitals

The whole comparison is row by row. These are the rows about MCP server.

Activity Monitor Vitals
What an assistant sees
Activity MonitorWhatever ps prints
VitalsApps, projects, sessions, ports and history, measured
Quitting
Activity Monitorkill, from the terminal
VitalsIt asks Vitals, Vitals asks you
What it is told
Activity MonitorEverything on the machine
VitalsWhat you allow, folders by name only
The past
Activity MonitorNothing
VitalsA day, a week or a year, and when the Mac was at a limit
Setup
Activity MonitorA server to find and configure
VitalsOne click per assistant in Settings → Integrations

The words behind it

What the numbers mean, from the Activity Monitor glossary.

Questions

The ones people ask about MCP server before they buy.

Which assistants work with it?

Claude, Claude Code, Codex, Cursor and any assistant that speaks MCP. Settings → Integrations adds the first four with one button each; any other takes the command shown there.

Can an assistant quit apps through Vitals?

Only through you. It asks Vitals, Vitals shows you what it wants to quit in a window of its own, and nothing closes until you say so. If you say no, it stays running.

Does it send my data to the assistant's maker?

Vitals answers the assistant on your Mac and sends nothing anywhere itself. What the assistant does with the answer is up to the assistant, the same as anything else you tell it.

Is it on by default?

No. It stays off until you turn it on in Settings → Integrations.

What can I stop an assistant from seeing?

System readings, apps, projects and history each have a switch in Settings → Integrations, for every assistant at once. Project folders can be given by name only.

Can safe requests go through without asking me?

Yes, for folders you choose. Add a project folder, or a folder that holds your projects, in Settings → Integrations, and what Vitals judges safe there is quit without asking. Everything else is still asked about.

How do I know what else will stop working?

Before anything is quit, the window names what is connected to it right now, such as Google Chrome or a process in another project, so you can see what else would break.

Can my assistant ask about last week?

Yes. It can ask how hard your Mac was pushed over a day, a week or a year, when it was at a limit, and which apps used the most over 90 days, 6 months or a year.

Read on

Guides that use this, and how Vitals compares with the apps people buy for it.

More of Vitals

All features

Menu bar monitor

CPU, memory, GPU, network, temperature and more, each its own item, red while under strain, with the apps behind every number one click away.

History

CPU, memory, energy, disk and network from the last hour to the last year, with the apps that used the most, hour by hour.

Alerts

An app keeping the CPU busy, growing in memory, or hammering the disk or network gets named before the fans tell you.

Get Vitals for $15 while the launch price lasts

50 left at this price. The regular price is $39. One payment, lifetime updates, 14-day refund.

Get Vitals for $15