01
Connect Medux MCP to Codex
Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_list_results tool is available.
Codex MCP tutorial · infra
How to list Medux result records with Codex MCP and Medux
Use Codex and Medux through MCP to list saved result records for the authenticated Medux account. This guide covers input preparation, the approval gate, task monitoring, and a concrete output check.
GET/api/app/v1/results
List saved result records for the authenticated user.
Open the List Results API reference →Codex-specific workflow
Run List Medux Results as a Codex MCP task
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_results, 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.
Codex prompt pattern
In this workspace, use medux_list_results through Medux MCP to list Medux result records.
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 result records and verify that the response uses the intended filters and account context.Approval gate
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.
Result verification
Let Codex monitor an asynchronous task until it reaches a terminal state, then save or report the matching result records. The final check is explicit: confirm that the response uses the intended filters and account context.
What this tutorial does
Medux operation
List saved result records for the authenticated user.
Agent workflow
Codex selects medux_list_results, presents the arguments for review, calls Medux, and reports the response.
Before you start
Authentication
- Authentication is required via Authorization header.
Preconditions
- Try it lists retained results for the current account.
- Results retention is limited; expired outputs are not returned.
Prompt Codex
Start with a clear instruction that names the Medux operation and the intended inputs.
Use Medux to run List Results. Review the required inputs, call medux_list_results, wait for the result if a task is returned, and report the output clearly.Request fields to review
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. |
media_type | string | Optional | Provide the value described in the API reference. |
capability_id | string | Optional | Provide the value described in the API reference. |
status | string | Optional | Allowed values: - RESULT STATUS UNDEFINED - Not specified. - READY - Result is ready. - RESULT PROCESSING - Result is still processing. - RESULT FAILED - Result generation failed. - RESULT EXPIRED - Result is expired. |
Step-by-step workflow
02
Prepare the required inputs
Identify the account, task, asset, or filter values the operation needs. Confirm that the Medux API key is available to the MCP connection.
03
Ask Codex to run List Results
Use one direct instruction with the intended values. Codex should select the Medux tool and show the proposed arguments before execution.
04
Review and approve the tool call
Check that the tool is medux_list_results and that each file ID, task ID, option, and output setting matches your request before approving it.
05
Check the Medux response
Review the returned records or status with the agent. Ask it to summarize identifiers and values that matter for the next step.
Workflow recap
User goal
↓
Codex selects medux_list_results
↓
Review inputs and approve the tool call
↓
Medux runs List Results
↓
Codex reports the response and outputFrequently asked questions
Can Codex use the Medux List Results API through MCP?
Codex can call the medux_list_results Medux MCP tool to list saved result records for the authenticated user. This guide covers the required inputs, approval flow, result handling, and the matching API reference.
Which MCP tool does this tutorial use?
This workflow uses medux_list_results. Review its arguments before approval and consult the API reference for the current contract.