Which AI tools are running on your work Mac?
Find the AI assistants, MCP connections and forgotten experiments on a work Mac. A practical inventory for small teams.
How do I find the AI agents and MCP servers on my Mac?
Start with installed assistants, then check the connections configured inside each one. Record who added them, what they connect to and whether the project still needs them. Compare that inventory with available activity records. An installed tool, a configured connection and a recorded action tell you three different things.
Start with the work, not the app count
You tried a coding assistant for a client project. Someone added a research connector. A freelancer connected a database for a demo. The project finished, but none of those decisions came with a reminder to remove access. A useful inventory starts by asking which work each connection still serves.
Choose one work Mac and list its owner, active clients and current projects. Then identify the assistants installed there, including desktop apps and tools used inside an editor or terminal. Ask the owner about experiments they stopped using. A familiar app name is not enough: the connections behind it matter.
Follow each assistant to its connections
MCP is a way for an assistant to use other tools. A connection might reach a project folder, a hosted service or a program running locally. Claude Code and VS Code both document ways to manage these connections. Their configuration locations and available controls differ, so inspect each assistant separately.
For each connection, record the assistant, server name, destination, business purpose and responsible person. Write “unknown” if the owner cannot identify a destination. Keep secrets out of this list: record where a credential is managed, never its value. A short table that someone maintains beats a large export nobody understands.
Three questions, three kinds of evidence
- Installed
Which assistants are on the Mac?
- Connected
Which tools are configured?
- Recorded
Which actions appear in activity?
Example workflow.
Separate what is connected from what happened
An example: a developer has a database connector configured in an old project. That tells you a connection exists in the configuration. It does not prove that the assistant queried the database, that the credentials still work or that information left the company. Those are separate questions with separate evidence.
Where activity records are available, check the time, tool, action and result. “Completed” describes a recorded execution phase; it does not mean the action was appropriate. Missing records do not prove nothing happened either. If a connection concerns you, inspect the relevant service’s permissions and logs before drawing a conclusion.
Give every connection an owner and a decision
Keep the connections required for current work. Review those with an unclear purpose, broad access or no responsible person. Remove unnecessary connections using the assistant’s settings, then review their credentials at the service that issued them. Removing a connection from one assistant is not the same as revoking its key.
Make the next review part of a real event: a contractor leaving, a client handover or a new assistant joining the approved tools. Tell people how to request a useful connector. If the only process is “do not install anything”, the inventory is likely to miss the tools people need.
Keep the view close to your work
Cybee brings installed AI tools, mapped MCP connections and recorded tool activity into the same conversation as the security of the Mac. After installation and connecting your assistant, start with /cybee. Suggested questions help you find a starting point without learning a security dashboard or remembering a list of commands.
Use that view to investigate the devices you have enrolled. It is not a promise to discover every cloud agent, reveal every API key or capture every action. Keep the service-side access review alongside it. The useful outcome is a list your team can explain, with fewer forgotten connections behind client work.
What to remember
- List assistants and their connections separately.
- Record purpose and ownership without copying secrets.
- Check access at the service before calling a connection removed.
Sources and further reading
Product scope and provider guidance can change. Check the linked source for your own setup.
Put it to work.
Continue with a practical guide or see how cybee helps with the work.