Connect Medux MCP to Codex
Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_list_voices tool is available.
Learn to list reusable AI voices with the Medux API through Codex or Claude MCP. Check inputs, tool calls, task status, and output.
GET/api/app/v1/clone/voices
List reusable voice assets owned by the authenticated user.
Open the List Voices 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 intended account context and any pagination settings, select medux_list_voices, 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_list_voices through Medux MCP to list reusable AI voices.
First inspect and identify the intended account context and any pagination settings.
Show me the exact tool arguments before execution.
After the task completes, return the voice asset records and verify that the returned list uses the intended account and pagination values.
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 voice asset records. The final check is explicit: confirm that the returned list uses the intended account and pagination values.
List reusable voice assets owned by the authenticated user.
Codex selects medux_list_voices, 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 List Voices. Review the required inputs, call medux_list_voices, 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 |
|---|---|---|---|
cursor | string | Optional | Provide the value described in the API reference. |
limit | int32 | 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_list_voices tool is available.
Identify the account, task, asset, or filter values the operation needs. Confirm that the Medux API key is available to the MCP connection.
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_list_voices and that each file ID, task ID, option, and output setting matches your request before approving it.
Review the returned records or status with the agent. Ask it to summarize identifiers and values that matter for the next step.
User goal
↓
Codex selects medux_list_voices
↓
Review inputs and approve the tool call
↓
Medux runs List Voices
↓
Codex reports the response and outputCodex can call the medux_list_voices Medux MCP tool to list reusable voice assets owned by the authenticated user. This guide covers the required inputs, approval flow, result handling, and the matching API reference.
This workflow uses medux_list_voices. 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 intended account context and any pagination settings before proposing medux_list_voices. 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 list reusable AI voices with Medux MCP.
Restate which input fulfills each role: the intended account context and any pagination settings.
Propose the medux_list_voices call and summarize its arguments before asking for approval.
When it finishes, return the voice asset records with a checklist confirming that the returned list uses the intended account and pagination values.
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 voice asset records plus a concise validation checklist confirming that the returned list uses the intended account and pagination values.
List reusable voice assets owned by the authenticated user.
Claude selects medux_list_voices, 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 List Voices. Review the required inputs, call medux_list_voices, 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 |
|---|---|---|---|
cursor | string | Optional | Provide the value described in the API reference. |
limit | int32 | 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_list_voices tool is available.
Identify the account, task, asset, or filter values the operation needs. Confirm that the Medux API key is available to the MCP connection.
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_list_voices and that each file ID, task ID, option, and output setting matches your request before approving it.
Review the returned records or status with the agent. Ask it to summarize identifiers and values that matter for the next step.
User goal
↓
Claude selects medux_list_voices
↓
Review inputs and approve the tool call
↓
Medux runs List Voices
↓
Claude reports the response and outputClaude can call the medux_list_voices Medux MCP tool to list reusable voice assets owned by the authenticated user. This guide covers the required inputs, approval flow, result handling, and the matching API reference.
This workflow uses medux_list_voices. Review its arguments before approval and consult the API reference for the current contract.