AI & MCP

AI-assisted authoring

Use an MCP-connected assistant to inspect and author Oraphim projects while keeping creative decisions, permissions, undo, and delivery verification under your control.

Updated August 27, 2026

AI-assisted authoring

An MCP-connected assistant can help operate Oraphim through the same project model you work with manually. Think of it as a fast technical collaborator: useful for structured changes and repetitive setup, but still subject to your creative review.

Ask for outcomes with boundaries

A strong request names the project resource and desired result. Examples:

  • "On timeline Interview_Main, add markers at these review timecodes and do not move clips."
  • "Create a 1920×1080 composition named LowerThird_A, add editable name/title text, and stop before changing the Edit timeline."
  • "List the current exportable resources and tell me which ones are 24 fps; do not mutate the project."
  • "Build the requested VFX node branch on the selected layer, validate it, and save only after reporting the resulting node IDs."

This is safer and more reproducible than a vague instruction that lets the assistant guess scope.

Inspect before mutate

For unfamiliar projects, begin in ReadOnly mode. Ask the assistant to report timelines, compositions, selected resources, dimensions, frame rates, or diagnostics. Once you know it is targeting the correct objects, increase permission only if the next step requires editing.

Review an authored change

After an AI-authored edit, inspect the changed timeline/graph/layer in Oraphim. Play through the affected range, check the Inspector, and verify that no unrelated resources moved. Use undo when a tool participates in the undo contract; for large changes, use project milestones as an additional safety net.

AI is optional

Oraphim remains usable as a normal creative application without connecting a general-purpose AI model. Local masking/fill/transcription models are separate from MCP, and manual Edit/Composition/Color/VFX/Audio/Export workflows remain first-class.

Delivery rule

Never approve an AI-authored result solely because the tool call returned success. Save/reopen structural work and independently inspect a rendered/exported file for anything that affects final delivery.