MCP tool surface

The certified production MCP registry reports 242 tools. The exact capability list can be queried from the running application, which is preferable to hard-coding assumptions in an agent integration.

Major tool families

• Project and resource inspection — active project, media, timelines, compositions, selections, capabilities, diagnostics.
• Timeline authoring — create/edit timeline resources, clips, timing, naming, and related operations.
• Composition/layer authoring — create compositions, layers, text/shapes, transforms, masks, effects, and graph-related operations.
• VFX/procedural authoring — node/graph operations, editable system construction, 3D/runtime bindings, preview and validation paths.
• Color — dedicated color tools plus project/color-resource inspection and mutation.
• Proxy/media — generate proxy, query proxy status, enable/disable proxy playback, cancel jobs, delete proxy caches.
• Export — list exportable resources, export a resource, legacy timeline/composition export compatibility, queue/status operations.
• Workflows — bounded multi-operation workflows exposed as explicit tools rather than arbitrary hidden project rewrites.
• Diagnostics and capabilities — MCP/runtime state, backend availability, project-active state, tool counts, and related health information.
• Focused UI automation — Oraphim-window focus recovery plus supported client-coordinate click, drag, text entry, and shortcut control for operations that genuinely require UI interaction.

Prefer model tools over screen automation

If a project-model tool exists, use it instead of clicking by coordinates. Model tools are easier to validate, less sensitive to window layout, and can participate in Oraphim's authoring/undo/persistence contracts.

Permission and transactions

Start with ReadOnly for discovery. Use edit/admin access only for mutation. For large authoring operations, save a milestone first, execute a bounded workflow, validate returned object/resource identities, inspect the result, then save the accepted project state.

Integration verification

A successful HTTP/JSON response is not enough. A robust integration verifies the resulting project resource, saves/reopens when persistence matters, captures or renders real pixels when visual output matters, and independently checks exported media when delivery matters. Oraphim's own MCP production certification follows that pattern.