Automation
Two automation surfaces ship in the CLI: direct control of the machine’s own desktop, and the MCP server that hands Cmdop’s tools to an AI assistant.
Automation commands are intentionally split by caller. Use cmdop os when a
human or script is controlling the local desktop. Use cmdop mcp when a local
assistant such as Claude Code or Codex needs a tool surface for machines and
fleet work.
cmdop osWindows, keyboard, mouse, clipboard, screenshots, and notifications.cmdop mcpRegister fleet tools with a local AI assistant.
For running an agent prompt on a schedule, see cmdop trigger. For running a packaged Skill, see cmdop skill.
Automation boundaries
| Surface | Runs where | Use it for |
|---|---|---|
cmdop os | This machine | Windows, keyboard, mouse, clipboard, screenshots, and notifications. |
cmdop mcp | Local assistant client | Exposing Cmdop tools to an MCP-capable assistant. |
cmdop trigger | Relay schedule | Running prompts later or repeatedly. |
cmdop skill | Agent runtime | Packaging repeatable task behavior. |
For remote command execution, start with cmdop connect or cmdop fleet; do not treat desktop automation as a general remote shell.
Last updated on
Cmdop