codex-computer-use-mcp
Related Servers
Alternatives to codex-computer-use-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceAn MCP server that gives AI agents real OS-level control of macOS, enabling them to click real buttons, type real keys, and observe rendered screens just like a human would.1MIT
- AlicenseNot gradedqualityAmaintenanceTurns ChatGPT into a local agent runtime on macOS, enabling shell execution, file editing, MCP server aggregation, tool discovery, and provider-backed subagents through a single MCP connection.243MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables integration of the ChatGPT macOS app with MCP clients like Cursor and Chatwise.17MIT
- AlicenseNot gradedqualityAmaintenanceA local macOS MCP server for AI Agents that exposes safe endpoints for shell commands, files, processes, macOS automation, browser control, and more.77MIT
- AlicenseNot gradedqualityCmaintenanceLocal MCP server bridging ChatGPT Web to local tools for file, shell, git, test, and process management with secure policy controls.MIT
- AlicenseAqualityDmaintenanceA local MCP server that delegates tasks to a subagent runtime via OpenAI-compatible interfaces, enabling file operations, command execution, and rollback of local file changes.5MIT
TDQS
Scored across 11 tools
Each tool maps to a distinct UI interaction such as clicking, typing, scrolling, dragging, or value setting, so an agent can generally pick the right one. The main overlap risk is between `type_text` and `press_key`, since both are keyboard interactions, and `perform_secondary_action` versus `click` could be confused when a secondary action is not clearly described.
Most tools follow a lowercase snake_case verb-first pattern such as `list_apps`, `get_app_state`, `type_text`, and `select_text`. The consistency is marred slightly by `computer_use_status`, which reads as a noun phrase rather than an imperative verb like `get_computer_use_status`, and by a few bare verbs like `click` and `drag`.
With 11 tools, the set is well-scoped for the stated purpose of computer use through screenshots, accessibility trees, keyboard input, and pointer actions. Every tool covers a needed capability without bloating the surface.
The tools collectively cover common end-to-end GUI workflows: observe state, click, type, press shortcuts, scroll, drag, set values, and select text. There are minor gaps such as no dedicated hover, app-launch, or app-close tool, but those can often be worked around with the existing pointer and keyboard actions.