How can an AI agent control Shōgun?

An MCP-compatible AI agent can use DCC-MCP to use 48 typed official-SDK tools to inspect motion-capture scenes, attributes, bounded channel data, optical cameras, and files, control timeline state, and run capability-gated processing. 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.

Shōgun MCP and Shōgun CLI

The Shōgun MCP endpoint and Shōgun CLI workflow share the same DCC-MCP adapter and tool catalog. Use dcc-mcp-cli with --dcc-type shogun to limit tool searches to Shōgun. Tools declare their inputs, outputs, and parameter types so arguments can be checked before a call.

dcc-mcp-cli search --query "inspect subjects, markers, skeletons, trajectories, hierarchy, transforms, attribute and channel names, bounded samples and gaps, optical cameras, and selection" --dcc-type shogun

What can an AI agent do in Shōgun?

• inspect subjects, markers, skeletons, trajectories, hierarchy, transforms, attribute and channel names, bounded samples and gaps, optical cameras, and selection.
• inspect or change explicit play and animation ranges, key-derived selections, and playback when the host exposes Timeline.
• inspect or update an allowlisted processing setting and run ROM labeling, calibration, QuickPost, or another bounded processing step only after the host confirms the official capability.

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 Shōgun 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 Shōgun 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 "inspect or change explicit play and animation ranges, key-derived selections, and playback when the host exposes Timeline", 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: "inspect or update an allowlisted processing setting and run ROM labeling, calibration, QuickPost, or another bounded processing step only after the host confirms the official capability". Report the instance, tool, result, and evidence path.

Current availability and official source

The current catalog lists shogun as the adapter identifier. Catalog definitions do not establish host acceptance; run dcc-mcp-cli dcc-types, then discover and describe the live instance's tools before operating.

• Shōgun 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.