Connect Medux MCP to Codex
Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_merge_audio tool is available.
Learn to merge audio files with the Medux API through Codex or Claude MCP. Check inputs, tool calls, task status, and output.
POST/api/app/v1/process/audio/merge_audio
Concatenate multiple audio files into one.
Open the Merge Audio 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 audio file IDs in the intended playback order, select medux_merge_audio, 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_merge_audio through Medux MCP to merge audio files.
First inspect and identify the audio file IDs in the intended playback order.
Show me the exact tool arguments before execution.
After the task completes, return the merged audio file and verify that every source clip appears once in the correct order without missing transitions.
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 merged audio file. The final check is explicit: confirm that every source clip appears once in the correct order without missing transitions.
Concatenate multiple audio files into one.
Codex selects medux_merge_audio, 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.
Concatenate multiple audio files into one.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 |
|---|---|---|---|
input_file_ids | array<string> | Required | Input audio file id list. |
model_id | string | Optional | Model Default: merge-audio-default. |
title | string | Optional | Optional task title. |
Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_merge_audio 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_merge_audio 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_merge_audio
↓
Review inputs and approve the tool call
↓
Medux runs Merge Audio
↓
Codex reports the response and outputCodex can call the medux_merge_audio Medux MCP tool to concatenate multiple audio files into one. This guide covers the required inputs, approval flow, result handling, and the matching API reference.
This workflow uses medux_merge_audio. 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 audio file IDs in the intended playback order before proposing medux_merge_audio. 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 merge audio files with Medux MCP.
Restate which input fulfills each role: the audio file IDs in the intended playback order.
Propose the medux_merge_audio call and summarize its arguments before asking for approval.
When it finishes, return the merged audio file with a checklist confirming that every source clip appears once in the correct order without missing transitions.
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 merged audio file plus a concise validation checklist confirming that every source clip appears once in the correct order without missing transitions.
Concatenate multiple audio files into one.
Claude selects medux_merge_audio, 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.
Concatenate multiple audio files into one.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 |
|---|---|---|---|
input_file_ids | array<string> | Required | Input audio file id list. |
model_id | string | Optional | Model Default: merge-audio-default. |
title | string | Optional | Optional task title. |
Add the Medux remote MCP endpoint to Claude, provide an authorized credential, and confirm that the medux_merge_audio 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_merge_audio 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_merge_audio
↓
Review inputs and approve the tool call
↓
Medux runs Merge Audio
↓
Claude reports the response and outputClaude can call the medux_merge_audio Medux MCP tool to concatenate multiple audio files into one. This guide covers the required inputs, approval flow, result handling, and the matching API reference.
This workflow uses medux_merge_audio. Review its arguments before approval and consult the API reference for the current contract.