System connectorMCP-first

Host-machine automation as its own connector boundary

System is Scout's host-automation connector for apps, dialogs, clipboard, keyboard, mouse, windows, screenshots, and accessibility-aware desktop workflows.

focustypeopencapture

See connector reference Browse connectors

The operating surface

Native windows, command palettes, accessibility outlines, keyboard traces, and desktop chrome for workflows that leave the browser sandbox.

A desktop command surface where windows, dialogs, input, clipboard, speech, and screenshots become intentional host-machine capabilities.

Identity

System is the moment an agent touches the actual operating environment.

Some workflows do not live in a browser tab. They cross native apps, dialogs, file pickers, windows, keyboard focus, and accessibility surfaces.

The system connector gives that world a boundary: powerful host-machine actions, but exposed as a named connector instead of hidden ambient control.

State

host environment

Signal

windows and accessibility

Loop

focus, input, confirm

Best for

Desktop automation and accessibility-aware host-machine workflows.

Window management, dialogs, clipboard, keyboard, mouse, screenshots, and system notifications.

Agent flows that must bridge beyond the browser into the operating system.

Runtime model

Automates the host machine through native system capabilities and accessibility surfaces.

Separates desktop automation from browser and Node connectors so each workflow can choose the minimum real surface it needs.

Treats dialogs, windows, input, and screenshots as first-class runtime operations instead of one-off utilities.

Auth model

Use the same Scout auth boundary as other public connectors, then expose system capabilities only to trusted workflows.

Grant host-machine automation intentionally. This connector should not ride along just because another connector is present.

Keep system access explicit so desktop automation, dialogs, clipboard, and window management remain auditable capabilities.

Capability atlas

A compact map of what this connector can do.

System exposes 14 commands across 1 capability groups. The full reference stays close, while this page keeps the connector's runtime shape easy to understand.

System

Automate the host machine through native system capabilities and accessibility APIs.

system-accessibilitysystem-appsystem-clipboardsystem-dialogsystem-keyboardsystem-menusystem-mousesystem-notify+6 more

Connection

Add the connector deliberately.

Add the hosted connector endpoint your MCP client needs. Each public connector stays separate so agent permissions and runtime boundaries remain explicit.

SnippetJSON

{
  "mcpServers": {
    "scout-system": {
      "type": "http",
      "url": "https://mcp.scout.i.ng/system"
    }
  }
}

Keep connector boundaries intentional

Dedicated connector pages should make capability boundaries memorable before the agent ever receives tools.

Browse all connectors Back to docs reference