How can an AI agent control OpenScreen?

An MCP-compatible AI agent can use DCC-MCP to inspect recording sources and run typed bounded record and export operations without desktop UI automation. The agent selects the correct application instance or integration, discovers available tools, and reads their parameter definitions before acting and checking the result. These typed tools declare their inputs, outputs, and parameter types.

What can an AI agent do in OpenScreen?

• inspect available OpenScreen recording sources.
• start one bounded recording through the configured executable.
• export and verify the requested recording artifact.

Capabilities change with the adapter version and loaded Skills. Search and describe tools first instead of guessing current tool names from this page.

Safe operating flow

1. Install and follow the public dcc-mcp Skill.
2. Inspect the existing CLI, adapter, and live hosts; obtain consent before installing software or changing system state.
3. Use health, dcc-types, and list to verify the Gateway and target instance.
4. Search and describe tools for the actual OpenScreen task, then follow every returned next_step.
5. Make one bounded change and verify it through host state, files, previews, logs, or rendered output.

dcc-mcp-cli health
dcc-mcp-cli dcc-types
dcc-mcp-cli list

Copyable prompt

Use the dcc-mcp Skill to connect to my OpenScreen session. Inspect the existing CLI, adapter, and live instance first; ask before installing software or changing system state. Search for and describe typed tools related to "start one bounded recording through the configured executable", then follow every returned next_step. Do not delete, overwrite, or publish existing work. Make the smallest verifiable change, then check the result against this requirement: "export and verify the requested recording artifact". Report the instance, tool, result, and evidence path.

Current availability and official source

The owning repository has independently released v0.1.1; it is not a host route in the verified Core 0.20.39 catalog. Source tests do not establish live Windows recording acceptance; unsupported window selection remains owned by dcc-cua and ui-control. This refresh verified release metadata, not a new live-host run.

• OpenScreen adapter repository: source of truth for installation, compatibility, host-specific capabilities, and troubleshooting.
• All AI + DCC control guides: return to every public application and pipeline integration.
• Agent workflow: shared discovery, call, validation, and diagnostic steps.

This page describes the shared Agent workflow. Each integration's repository owns its installation, API, and compatibility details.