Computer MCP / Docs / Uninstall
Uninstalling Computer MCP, and exactly what data it touches
Three steps to remove it, the one file it ever writes, what each macOS permission is for, and the thing that matters most: it makes no network calls at all, and you can check that yourself in one command.
Remove it in three steps
- Unregister it from your MCP client.
claude mcp remove computerfor Claude Code,codex mcp remove computerfor Codex, or delete the"computer"block from~/.cursor/mcp.json. The server is started by your client on demand, so once it is unregistered nothing runs it again. - Delete the one file it created.
rm -rf ~/.local/state/computer-mcpremoves the audit log and its directory. That is the only thing it has ever written outside the npm cache. - Revoke the two macOS permissions, if nothing else needs them: System Settings, Privacy & Security, then Accessibility and Screen Recording. Remove the app you granted them to, or just untick it.
There is no installer, no daemon, no launch agent and no login item, so there is nothing
else to hunt for. If you want to be thorough, npx keeps its own package cache
and npm cache clean --force clears it, though that affects every package and is
rarely worth doing for this reason alone.
Exactly what it touches while installed
| What | Why, and what is in it |
|---|---|
~/.local/state/computer-mcp/audit.jsonl |
The log that only grows, mode 0600 so only your user can read it. One line per call: the tool, the target app, the outcome, and a per-server session mark. Typed text is stored as a scrambled fingerprint, with a random ingredient so it cannot be looked up, never in clear. The salt is random per run and is never written down, which means two actions can be compared within a run and not across runs. That is deliberate: a fingerprint without that random ingredient, of a short password, can be guessed offline by whoever ends up holding the log. |
| Accessibility permission | Reads the accessibility tree: what an element is, where it is, and whether a field is
marked secure. It is also what lets computer_press and
computer_set_value act on a background window without moving your pointer. |
| Screen Recording permission | Takes the screenshot. The redaction happens on the bitmap in memory, before any file is written, so the unredacted image never exists on disk. |
| The npm package cache | Whatever npx normally keeps. Nothing specific to this server. |
That is the whole list. No preferences file, no database, no hidden directory in your home
folder, no crash reporter. If you would rather check than trust: the only write in the whole
source is in mcp-server/audit.js, and it writes to that one path.
The part that matters: nothing is sent to us
There is no account, no API key, no licence check, no telemetry and no update ping. The server makes no network calls of its own at all. The only thing that talks to a model is the MCP client you were already running, and it talks to whichever provider you already chose.
You do not have to take our word for it. The source is MIT and the check is one command:
git clone https://github.com/Agent360dk/computerMCP
cd computerMCP
grep -rnE "fetch\\(|https?://|net\\.|axios" mcp-server/ helper/Sources/What comes back is bundle identifiers and documentation links, nothing that opens a socket. If you ever find an actual outbound call in there, that is a bug report we would want immediately, and we would treat it as the most serious kind there is.
Before you go
If you are uninstalling because something did not work, troubleshooting covers the failures that look like bugs and are not, chiefly a full-screen app hiding every other window from both the accessibility API and the screenshot. And if the tool was simply wrong for the job, when not to use it says which tool we would have pointed you at instead. Either way, an issue telling us what happened is worth more to us than a silent removal.
FAQ
How do I completely remove Computer MCP?
Three steps: unregister it from your MCP client (claude mcp remove computer, codex mcp remove computer, or delete the block from ~/.cursor/mcp.json), delete the directory ~/.local/state/computer-mcp, and revoke the Accessibility and Screen Recording permissions if nothing else needs them. There is no installer, daemon or login item.
What files does it leave on my Mac?
Exactly one: ~/.local/state/computer-mcp/audit.jsonl, a log that only grows, mode 0600. No preferences file, no database, no hidden directory, no crash reporter. The only write in the entire source is in mcp-server/audit.js.
Is my typed text stored in the log?
Not in clear. Each typed action is recorded as a scrambled fingerprint, with a random ingredient so it cannot be looked up. The salt is random per run and never written down, so two actions compare within a run and not across runs. Without that random ingredient, a short password could be worked out offline by whoever ended up with the log, which is why it is salted.
Does Computer MCP send anything to Agent360?
No. There is no account, no API key, no licence check, no telemetry and no update ping. The server makes no network calls of its own. You can verify it yourself: clone the repo and grep for fetch, http, net or axios in mcp-server/ and helper/Sources/.
Will uninstalling delete my audit history?
Deleting the state directory does, and nothing else will. If you want to keep the record, copy the file somewhere first. It is plain JSON Lines and reads fine in any text editor.
Do I have to revoke the macOS permissions?
Only if nothing else needs them. They are granted to whichever app was the responsible process, often your terminal or your MCP client, and other tools may rely on the same grant. Removing the server does not use them either way.
Can I reinstall later without redoing the permissions?
Usually yes, if you grant them to the same app. We have not measured whether upgrading the package re-prompts: the helper is ad-hoc signed, so its code identity changes with every build, and if macOS keys the grant to the helper rather than the host app an upgrade could silently revoke it. Issue #4 tracks that measurement.