# Computer Use [Health: Active]

**Category:** 🖥️ OS Automation  
**Repository:** https://github.com/munimtechnologies/computer-use  
**GitHub Stars:** 18  
**npm Downloads (last month):** 2591  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/computer-use-3

## Description
Accessibility-first desktop control for any agent: background input, agent pointer, zoom, Chrome.

## Tools
Capabilities this server exposes over MCP:

- **wait_timeout_ms** — defaults to `8000`, accepts integers `0`–`10000`; `0` checks

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "computer-use": {
    "command": "npx",
    "args": ["-y","munim-computer-use"]
  }
}
```

## Documentation

## What Computer Use does

Computer Use gives MCP-compatible agents a computer-use backend for operating a desktop as a person would. It reads user interfaces through accessibility trees, then performs interaction in the background so the user's mouse remains available. The server also exposes an agent pointer to show where work is happening and can zoom in on small text.

The supported operating systems are macOS, Windows, and Linux. Browser automation covers tabs in a signed-in Chrome session. The server is intended for coding agents and can work with any model; interaction does not require a vision model.

## How it works

Agents inspect the desktop through application state and act on interface elements identified from that state. A typical workflow uses `get_app_state` to read the current UI, performs clicks or text entry against the resulting element identifiers, and calls `screenshot` to verify the result.

Input is sent in the background rather than through the user's active mouse position. This makes it suitable for workflows that run while a person continues using the computer. The agent pointer provides a visible indication of the operation location, while zoom helps with interfaces containing small text.

## Setup and configuration

Download the latest platform binary from the project's releases, or build the project from source. Place the executable on `PATH`; the documented locations include `/usr/local/bin/munim-computer-use` on macOS and `%LOCALAPPDATA%\\Programs\\munim-computer-use\\munim-computer-use.exe` on Windows.

On macOS, run `munim-computer-use request-permissions` once to request Accessibility and Screen Recording access. Register the executable as an MCP stdio server in the client of your choice. The npm package can also launch the signed binary on first use:

```sh
npx -y munim-computer-use
```

Claude Code and Codex can register that command through their MCP configuration commands. Cursor uses an MCP JSON configuration file, either globally at `~/.cursor/mcp.json` or for a repository at `.cursor/mcp.json`.

## Tools and capabilities

- Read application interfaces through accessibility state.
- Click and type using background input.
- Show an agent pointer during computer interaction.
- Zoom interface content for easier reading.
- Control tabs in a signed-in Chrome session.
- Capture screenshots for state verification.
- Configure `wait_timeout_ms` from `0` through `10000` milliseconds; the default is `8000`, and `0` performs an immediate check.

## Limitations and notes

Desktop access depends on the permissions required by the operating system. On macOS, Accessibility and Screen Recording permissions must be granted before use. Chrome workflows assume a signed-in Chrome session. The server communicates over MCP stdio, so the client must be able to launch a local command. Its documented platform coverage is macOS, Windows, and Linux.

_Full upstream README: https://allmcps.com/mcp/computer-use-3/readme_