Connect Medux MCP to Codex
Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_create_video_by_project tool is available.
Learn to generate video from a Medux project with the Medux API through Codex or Claude MCP. Check inputs, tool calls, task status, and output.
POST/api/app/v1/generate/video/by_project
Start video generation from an existing Flyworks provider project.
Open the Create Video by Project API reference →The Medux operation and request fields are shared. Switch tabs for the client-specific prompt, approval pattern, screenshots, and walkthrough.
Codex-specific workflow
Use the active workspace as the source of truth. Ask Codex to identify the project ID and supported generation options, select medux_create_video_by_project, and keep the Medux task ID and returned output with the rest of the project. Naming the input roles and the expected result prevents an agent from guessing which file should be used where.
In this workspace, use medux_create_video_by_project through Medux MCP to generate video from a Medux project.
First inspect and identify the project ID and supported generation options.
Show me the exact tool arguments before execution.
After the task completes, return the new video-generation task and verify that the task references the intended project and reaches the expected state.
Before approving the call, compare the selected tool, file or asset IDs, ordering, timing, and output settings with the request. If a local filename was mapped to an uploaded Medux file ID, keep that mapping visible so it can be audited later.
Let Codex monitor an asynchronous task until it reaches a terminal state, then save or report the new video-generation task. The final check is explicit: confirm that the task references the intended project and reaches the expected state.
Start video generation from an existing Flyworks provider project.
Codex selects medux_create_video_by_project, presents the arguments for review, calls Medux, and reports the response.
Start with a clear instruction that names the Medux operation and the intended inputs.
Use Medux to run Create Video by Project. Review the required inputs, call medux_create_video_by_project, wait for the result if a task is returned, and report the output clearly.Confirm these values before approving the MCP tool call. The linked API page remains the source of truth for current limits and response semantics.
| Field | Type | Requirement | Purpose |
|---|---|---|---|
project_id | string | Optional | Provide the value described in the API reference. |
title | string | Optional | Provide the value described in the API reference. |
Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_create_video_by_project tool is available.
Prepare the source files, asset IDs, text, or settings required by the operation. Upload local media first when the tool requests file IDs.
Use one direct instruction with the intended values. Codex should select the Medux tool and show the proposed arguments before execution.
Check that the tool is medux_create_video_by_project and that each file ID, task ID, option, and output setting matches your request before approving it.
If Medux returns an asynchronous task, let the agent monitor it until completion; otherwise review the immediate response and save any result identifiers or output URLs.
User goal
↓
Codex selects medux_create_video_by_project
↓
Review inputs and approve the tool call
↓
Medux runs Create Video by Project
↓
Codex reports the response and outputCodex can call the medux_create_video_by_project Medux MCP tool to start video generation from an existing Flyworks provider project. This guide covers the required inputs, approval flow, result handling, and the matching API reference.
This workflow uses medux_create_video_by_project. Review its arguments before approval and consult the API reference for the current contract.
Claude-specific workflow
Keep the goal, source assets, and constraints together in the conversation. Ask Claude to restate the project ID and supported generation options before proposing medux_create_video_by_project. That context checkpoint makes the file roles and desired outcome easy to correct before any Medux call is approved.
Using the assets and requirements in this conversation, help me generate video from a Medux project with Medux MCP.
Restate which input fulfills each role: the project ID and supported generation options.
Propose the medux_create_video_by_project call and summarize its arguments before asking for approval.
When it finishes, return the new video-generation task with a checklist confirming that the task references the intended project and reaches the expected state.
Have Claude summarize the intended transformation, identify every source asset by role, and list the important constraints. Review that summary together with the proposed tool arguments; correct the conversation first if a file, order, time range, or setting is ambiguous.
Keep the Medux task ID in the conversation while Claude checks progress. When processing ends, ask for the new video-generation task plus a concise validation checklist confirming that the task references the intended project and reaches the expected state.
Start video generation from an existing Flyworks provider project.
Claude selects medux_create_video_by_project, presents the arguments for review, calls Medux, and reports the response.
Start with a clear instruction that names the Medux operation and the intended inputs.
Use Medux to run Create Video by Project. Review the required inputs, call medux_create_video_by_project, wait for the result if a task is returned, and report the output clearly.Confirm these values before approving the MCP tool call. The linked API page remains the source of truth for current limits and response semantics.
| Field | Type | Requirement | Purpose |
|---|---|---|---|
project_id | string | Optional | Provide the value described in the API reference. |
title | string | Optional | Provide the value described in the API reference. |
Add the Medux remote MCP endpoint to Claude, provide an authorized credential, and confirm that the medux_create_video_by_project tool is available.
Prepare the source files, asset IDs, text, or settings required by the operation. Upload local media first when the tool requests file IDs.
Use one direct instruction with the intended values. Claude should select the Medux tool and show the proposed arguments before execution.
Check that the tool is medux_create_video_by_project and that each file ID, task ID, option, and output setting matches your request before approving it.
If Medux returns an asynchronous task, let the agent monitor it until completion; otherwise review the immediate response and save any result identifiers or output URLs.
User goal
↓
Claude selects medux_create_video_by_project
↓
Review inputs and approve the tool call
↓
Medux runs Create Video by Project
↓
Claude reports the response and outputClaude can call the medux_create_video_by_project Medux MCP tool to start video generation from an existing Flyworks provider project. This guide covers the required inputs, approval flow, result handling, and the matching API reference.
This workflow uses medux_create_video_by_project. Review its arguments before approval and consult the API reference for the current contract.