Which AI tools are on your work Mac? And what they can reach.

How do I find the AI agents and MCP servers on my Mac?

Start with the assistants installed on the Mac. Then open each one and list the connections set up inside it. Write down who added each connection, what it reaches and whether the project still needs it.

Then compare that list with the activity that was actually recorded. An installed tool, a 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 ended, but none of those choices came with a reminder to remove the access. So a useful inventory starts with one question: which work does each connection still serve?

Pick one work Mac. Write down its owner, the clients they work for and the current projects. Then find the assistants installed there, including desktop apps and the tools that run inside an editor or the terminal. Ask the owner about experiments they stopped using.

Follow each assistant to its connections.

MCP is the open standard that lets an assistant use other tools. A connection might reach a project folder, a hosted service or a program running on the Mac. Claude Code and VS Code both document how to manage these connections. Each assistant keeps them in a different place, with different controls, so check each one on its own. If you do not work in these tools yourself, do this step with the developer who does, or let cybee list them.

For each connection, write down the assistant, the server name, where it points, the business reason and the person responsible. If the owner cannot say where a connection points, write “unknown”. Keep secrets out of this list: note where a key is managed, never the key itself. A short table that someone keeps up to date beats a large export nobody understands.

Provider guidance: Claude Code: connect tools with MCP · VS Code: manage MCP servers

Separate what is connected from what happened.

Take an example. A developer has a database connector set up in an old project. That tells you a connection exists in the settings. It does not prove that the assistant queried the database, that the key still works or that any information left the company. Those are separate questions, with separate evidence.

Where activity records exist, check the time, the tool, the action and the result. “Completed” means the action reached that step in the record. It does not mean the action was appropriate. And missing records do not prove that nothing happened. If a connection worries you, look at that service’s permissions and logs before you draw a conclusion.

Give every connection an owner and a decision.

Keep the connections your current work needs. Review the ones with an unclear purpose, broad access or nobody responsible. Remove the ones nobody needs in the assistant’s own settings, then check their keys at the service that issued them. Removing a connection from one assistant does not cancel its key.

Tie the next review to a real event: a contractor leaving, a client handover or a new assistant joining the tools you approve. Tell people how to ask for a connector they need. If the only rule is “do not install anything”, the inventory will probably miss the tools people actually use.

Keep the view close to your work.

cybee lists the AI tools installed on your Macs, the connections set up in each one and the tool activity it recorded, in the same conversation as the rest of your Mac’s security. After you install it and connect your AI assistant, type /cybee. cybee is itself one of these connections: a tool your AI assistant uses through MCP. What leaves your Mac is listed on the security page. Suggested questions give you a place to start. cybee has no dashboard. Your AI assistant builds any view you ask for.

Use that view to look into the Macs you have enrolled. It does not promise to find every cloud agent, reveal every API key or capture every action, so keep checking access at each service as well. What you want at the end is a list your team can explain, with fewer forgotten connections behind client work.

What to remember.

• List the assistants and their connections separately.
• Write down the purpose and the owner. Never copy a secret into the list.
• Check access at the service before you call a connection removed.

Sources and further reading.

Written by cybee for small teams. Product scope and provider guidance can change, so check the linked source for your own setup.

• Claude Code: connect tools with MCP
• VS Code: manage MCP servers
• cybee: AI agents and MCP connections