Computer MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 60 installs a week from npm. Last commit 7 Nov 2026.
macOS computer use with the guardrails on: passwords blacked out, writes need consent, all logged.
We read the source, 6 d ago · rules 995398eba69f
A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.
const barn = spawn(hj, a, { stdio: ['ignore', 'pipe', 'pipe'] });
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
[/^Bash\((\/[\w/.-]*\/)?(sudo|doas)(\s*\*|:\*|\s+(\/\S*\/)?((ba|z|k|c|da|fi|tc)?sh|python\d*|node|ruby|perl|osascript|open)\b)/, 'runs commands as root - anything, including clicking and sending without this server'],
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
postinstall: node bin/postinstall.js || true
execFile(bin, args, { timeout, maxBuffer: 32 * 1024 * 1024 }, (err, stdout, stderr) => {
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
k = subprocess.run(['node', proeve], capture_output=True, text=True, timeout=600, env={**os.environ, 'TMPDIR': tmp + '/'})
el.innerHTML = html;
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add computer-mcp -- npx -y @agent360/computer-mcp
{
"mcpServers": {
"computer-mcp": {
"command": "npx",
"args": [
"-y",
"@agent360/computer-mcp"
]
}
}
}
[mcp_servers.computer-mcp]
command = "npx"
args = ["-y", "@agent360/computer-mcp"]
{
"mcpServers": {
"computer-mcp": {
"command": "npx",
"args": [
"-y",
"@agent360/computer-mcp"
]
}
}
}
{
"servers": {
"computer-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@agent360/computer-mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
CMCP_MODE (readonly | ask (default) | allow), CMCP_ASK_TIMEOUT (Seconds a consent dialog waits before refusing. Default 60).
FHIR MCP server with SMART Backend Services, response compaction, FHIRPath, and guarded writes.
Share what AI agents write with the right people only: your company, specific emails or a password.
Let any AI agent operate desktop apps on macOS, Windows and Linux, in the background and safely.
Local macOS Computer Use MCP server with screenshots, AX trees, and app actions.
Arc browser MCP for macOS: agent window, snapshots, DevTools input, guardrails
Windows computer use in the background: desktop apps driven without your mouse or keyboard.
Run sudo commands with a Fernet-encrypted password bound to machine-id + user.
Open-source computer use for macOS agents.
Answers built from our own checks of this server.