open-computer-use — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track computer-use client compatibility and published action boundaries as the host changes

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Agents that need cross-platform desktop computer-use control.

What we know

An open-source computer-use service wrapped as MCP for macOS, Linux and Windows desktop actions.

Maintenance / activity evidence

Observed Sep 29, 2026 (UTC)release: prepare v0.3.6

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Desktop/screen permissions. Writes: Mouse/keyboard/application actions.
Authentication not yet verified.
Sensitive access: Screen content, Desktop applications

Computer-use control can interact with sensitive applications and authenticated sessions.

Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

2,341 repository stars · 11.7k package downloads / 30 days

Stars observed Oct 6, 2026. Downloads observed Oct 6, 2026.

All limitations / Review context

What desktop actions, sandbox limits, and MCP connection guidance are current?

The bounded official-source review found no disclosed material public-tracking blocker for the documented computer-use MCP host; desktop action scope remains an uncertainty and was not treated as a safety certification.

Computer-use control can interact with sensitive applications and authenticated sessions.
Desktop/screen permissions.
Screen and application content is exposed to the connected agent.
Reviewed write actions: Mouse/keyboard/application actions
Sensitive access: Screen content, Desktop applications
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Computer-use actions can have consequential effects; the repository's fetched security document is a template and no independent runtime or permission audit was performed.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Desktop control is broad authority.
macOS requires Accessibility and Screen Recording permissions.

Original activity observations

2026-09-29T03:46:48Z: release: prepare v0.3.6

Technical identity

github.com/ifuryst/open-codex-computer-use

Exact implementation source: https://github.com/ifuryst/open-codex-computer-use ↗
Reviewed resource type: MCP Server
Repository identity: iFurySt/open-codex-computer-use
Package identity: npm:open-computer-use

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
ifuryst/open-codex-computer-use
Recorded repository material and project history.
Includes references whose attribution is not established.
Package registry ↗
open-computer-use
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 13, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
publisher documented install or connect · Publisher instructions
npm i -g open-computer-use open-computer-use install-codex-mcp
Configure / authenticate
Publisher instructions
On macOS grant Accessibility/Screen Recording once; the client may alternatively register stdio `open-computer-use mcp`.
Advanced configuration · claude desktop json · Publisher instructions
claude desktop json · Publisher instructions
{ "mcpServers": { "open-computer-use": { "args": [ "mcp" ], "command": "open-computer-use" } } }
Check connection
Suggested check
Inspect tool discovery through Codex; do not perform desktop manipulation for verification.
Remove / uninstall / revoke
MCP100 setup guide
Remove open-computer-use entry from Codex MCP configuration; `npm uninstall -g open-computer-use` to remove CLI if desired.
MCP100 client-scope guidance: each CLI removal example targets only its named client and exact registered entry. Package names, Desktop/Cursor configuration keys and Codex/Claude registration names may differ; use the entry you actually registered. Client removal does not revoke provider credentials.
claude mcp remove open-computer-use

Official Documentation & Sources

What it does

An open-source computer-use service wrapped as MCP for macOS, Linux and Windows desktop actions.

Capability: Browser Automation
Resource type: MCP Server
Best fit: Agents that need cross-platform desktop computer-use control.

Representative uses

Control desktop applications
Inspect UI state
Run computer-use actions from coding agents
Use JavaScript evaluation where supported

Limitations

Desktop control is broad authority.
macOS requires Accessibility and Screen Recording permissions.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Desktop/screen permissions.
Data handling: Screen and application content is exposed to the connected agent.
Cost: free
Risk and cautions: Computer-use control can interact with sensitive applications and authenticated sessions.

Access scope and cautions

Write actions: Mouse/keyboard/application actions
Sensitive access: Screen content Desktop applications
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Control desktop applications; Inspect UI state; Run computer-use actions from coding agents; Use JavaScript evaluation where supported.

Can it modify data or perform write operations?

Documented write actions include: Mouse/keyboard/application actions. Recorded permission boundary: Desktop/screen permissions.

What data-handling boundary should I consider?

Screen and application content is exposed to the connected agent. Recorded sensitive-access context: Screen content; Desktop applications.

What limitations and risks should I check before use?

Computer-use control can interact with sensitive applications and authenticated sessions. Desktop control is broad authority. macOS requires Accessibility and Screen Recording permissions. Computer-use actions can have consequential effects; the repository's fetched security document is a template and no independent runtime or permission audit was performed. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

iFurySt is listed as Community implementation in MCP100’s current evidence.