Control the DFCine Canvas with Codex

After completing this guide, you can use natural language in Codex to read and operate the canvas currently open in DFCine.

Before You Begin

Make sure that:

• DFCine is installed and activated.
• A project and canvas are open in DFCine.
• You are using Windows and can open PowerShell.
• You do not share your local DFCine control token or complete configuration script with anyone.

Step 1: Download and Install Codex

Visit the official OpenAI Codex page, download and install Codex as instructed, and then sign in with your OpenAI account.

Step 2: Generate the Codex Configuration Script in DFCine

1. Open DFCine and enter a project canvas.
2. Open DFCine Settings.
3. Select MCP Agent.
4. Click Regenerate Token.
5. Find the Codex Global Integration section.
6. Click Copy Script next to the complete configuration script. The button displays Copied when successful.

Next, open Windows PowerShell:

1. Press the Win key and search for PowerShell.
2. Open Windows PowerShell or PowerShell.
3. Paste the complete script into the window.
4. Press Enter to run it.

When the command succeeds, PowerShell confirms that the DFCine MCP configuration was written to the Codex configuration file and asks you to reopen the terminal or restart Codex.

The script automatically adds or updates the MCP server named dfcine in Codex. You do not need to edit the configuration file manually.

If you regenerate the token later, copy and run the latest script again, then restart Codex. The old token becomes invalid immediately.

Step 3: Enable the DFCine MCP Service

Return to Settings > MCP Agent in DFCine:

1. Select Enable.
2. Click Save MCP Settings.
3. Keep DFCine, the current project, and the canvas open.

The default local service address is http://127.0.0.1:38765/mcp. You normally do not need to change the local port.

Step 4: Check the DFCine Server in Codex

If Codex is already open, exit it completely and reopen it so that the new configuration takes effect.

1. Open Codex.
2. Click Settings in the lower-right corner.
3. Open the Settings menu.
4. Select MCP Servers.
5. Find dfcine in the server list.

If dfcine is listed and enabled normally, Codex has loaded the DFCine MCP configuration.

Step 5: Test the MCP Connection

Create a new conversation in Codex and enter:

Which MCP services are available for the DFCine canvas? List the DFCine tools you can currently use.

When the connection is working, Codex returns tools whose names begin with dfcine_. These may include tools for reading canvas information, listing nodes, reading the selected node, writing node prompts, reading node parameters, or running nodes.

You can also enter:

Read the current DFCine canvas information and tell me which node is selected.

If Codex returns the current canvas or node information, the configuration is complete.

Step 6: Control the Canvas with Codex

You can now describe the task you want Codex to perform. For example:

Read the selected DFCine node and its workflow instructions. Optimize the prompt for the current node, preview the changes first, and write them to the node only after confirmation.

Or enter:

Read the node list on the current canvas and explain which MCP operations are available for each node.

Codex can only use the MCP features currently exposed and authorized by DFCine. DFCine will continue improving its canvas MCP capabilities to make Agent interactions smoother.

Troubleshooting

dfcine Does Not Appear in Codex

• Confirm that you ran the complete configuration script in PowerShell.
• Exit Codex completely and reopen it.
• Return to DFCine, copy the script again, and rerun it.

dfcine Appears but Cannot Read the Canvas

• Confirm that DFCine is running.
• Confirm that Enable is selected and Save MCP Settings was clicked.
• Confirm that a project and canvas are open in DFCine.
• If you regenerated the token, run the latest script and restart Codex.

Connection Failed or Server Unavailable

• Keep DFCine open. Its MCP service is available only while DFCine is running and MCP Agent is enabled.
• Check that DFCine and Codex use the same port.
• If you changed the local port, copy and run the configuration script again.

The PowerShell Script Had No Effect

• Check PowerShell for red error messages.
• Confirm that you copied the complete script from Codex Global Integration.
• Restart Codex after the script succeeds, then check the MCP server list again.