Workflow Automation with MCP

While the Copilot is great for interactive tasks, the true power of ORAPHIM's Model Context Protocol integration lies in headless workflow automation.

Scripting and Tools

ORAPHIM allows MCP servers to execute custom tools on the user's machine. By default, the software exposes a rich set of Python APIs (e.g., update_timeline_modes.py, add_text_render.py) that the AI can call.

Automated Dailies

If you are working on a massive film set, you can configure an MCP workflow to automatically process dailies overnight:

1. The MCP server monitors a watch folder for new .braw or .r3d camera files.
2. It sends a command to ORAPHIM to import the files.
3. It applies a standard Rec.709 LUT.
4. It syncs the audio based on timecode.
5. It renders the proxies to an external drive.

The Automation Node

In the Node Graph, you can drop an Automation Node. This node acts as a bridge, sending the current frame data to an external MCP server, asking the AI to process it, and waiting for the response.

Use Case: Connecting a custom enterprise Python script that automatically detects and blurs license plates on moving cars, frame by frame, utilizing ORAPHIM's internal C++ tracking engine in tandem with the external AI logic.