Connect Medux MCP to Codex
Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_list_assets tool is available.
Use Codex and Medux through MCP to list assets owned by the authenticated Medux account. This guide covers input preparation, the approval gate, task monitoring, and a concrete output check.
GET/api/app/v1/assets
List assets owned by the authenticated user.
Open the List Assets API reference →Codex-specific workflow
Use the active workspace as the source of truth. Ask Codex to identify the intended account context and any pagination or filter settings, select medux_list_assets, 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_assets through Medux MCP to list Medux assets.
First inspect and identify the intended account context and any pagination or filter settings.
Show me the exact tool arguments before execution.
After the task completes, return the matching asset records and verify that the response uses the intended filters and account context.
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 matching asset records. The final check is explicit: confirm that the response uses the intended filters and account context.
List assets owned by the authenticated user.
Codex selects medux_list_assets, 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 Assets. Review the required inputs, call medux_list_assets, 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. |
category | string | Optional | Allowed values: - CATEGORY UNDEFINED - Not specified. - MEDIA - Uploaded source media. - AVATAR - Reusable avatar asset. - VOICE - Reusable voice asset. |
status | string | Optional | . assethpb.Status:\ ... enums:\ ..... STATUS UNDEFINED\ ..... PROCESSING\ ..... ACTIVE\ ..... LOCKED\ ..... EXPIRING SOON\ ..... EXPIRED\ ..... DELETED |
Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_list_assets 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_assets 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_assets
↓
Review inputs and approve the tool call
↓
Medux runs List Assets
↓
Codex reports the response and outputCodex can call the medux_list_assets Medux MCP tool to list 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_assets. Review its arguments before approval and consult the API reference for the current contract.
Quick answer
Codex can use medux_list_assets through Medux MCP to list assets owned by the authenticated Medux account. The workflow identifies the exact inputs, reviews the tool arguments, monitors processing, and verifies the returned result.
Codex can use medux_list_assets through Medux MCP to list assets owned by the authenticated Medux account. The workflow identifies the exact inputs, reviews the tool arguments, monitors processing, and verifies the returned result.
Related topics: List Medux Assets · List Medux Assets with Codex MCP · Medux MCP tutorial
Build with the API
Use the API reference to automate this workflow, or follow the matching guide in our official GitHub repository.