01
Connect Medux MCP to Codex
Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_get_task tool is available.
Codex MCP tutorial · infra
How to get a Medux task by ID with Codex MCP and Medux
Use Codex and Medux through MCP to return a single Medux task record by its ID. This guide covers input preparation, the approval gate, task monitoring, and a concrete output check.
Codex-specific workflow
Run Get a Medux Task by ID as a Codex MCP task
Use the active workspace as the source of truth. Ask Codex to identify the exact task ID, select medux_get_task, 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_get_task through Medux MCP to get a Medux task by ID.
First inspect and identify the exact task ID.
Show me the exact tool arguments before execution.
After the task completes, return the matching task record and verify that the response ID matches the request and the status is interpreted correctly.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 task record. The final check is explicit: confirm that the response ID matches the request and the status is interpreted correctly.
What this tutorial does
Medux operation
Return one task record by its ID.
Agent workflow
Codex selects medux_get_task, presents the arguments for review, calls Medux, and reports the response.
Before you start
Authentication
- Authentication is required via Authorization header.
Preconditions
- Requires a task id from account history or task creation responses.
- Useful for account-side history views.
Prompt Codex
Start with a clear instruction that names the Medux operation and the intended inputs.
Use Medux to run Get Task. Review the required inputs, call medux_get_task, 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 |
|---|---|---|---|
task_id | string | Required | Provide the value described in the API reference. |
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 Get Task
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_get_task and that each file ID, task ID, option, and output setting matches your request before approving it.
05
Check the Medux response
Ask the agent to report the task status, result references, errors, and next action in a concise summary.
Workflow recap
User goal
↓
Codex selects medux_get_task
↓
Review inputs and approve the tool call
↓
Medux runs Get Task
↓
Codex reports the response and outputFrequently asked questions
Can Codex use the Medux Get Task API through MCP?
Codex can call the medux_get_task Medux MCP tool to return one task record by its ID. 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_get_task. Review its arguments before approval and consult the API reference for the current contract.