Learn to convert Word to PDF with the Medux API through Codex or Claude MCP. Check inputs, tool calls, task status, and output.
Watch the complete workflow: convert Word to PDF with Codex, Claude, MCP, and Medux.Watch on YouTube ↗
Choose your AI client
Follow the Codex or Claude workflow
The Medux operation and request fields are shared. Switch tabs for the client-specific prompt, approval pattern, screenshots, and walkthrough.
Codex-specific workflow
Run Convert Word to PDF as a Codex MCP task
Use the active workspace as the source of truth. Ask Codex to identify the source Word file ID and the desired output name, select medux_word_to_pdf, 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_word_to_pdf through Medux MCP to convert Word to PDF.
First inspect and identify the source Word file ID and the desired output name.
Show me the exact tool arguments before execution.
After the task completes, return the converted PDF and verify that the PDF opens, page order is intact, and the document content is readable.
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 converted PDF. The final check is explicit: confirm that the PDF opens, page order is intact, and the document content is readable.
What this tutorial does
Medux operation
Convert a Word document (.docx) to PDF.
Agent workflow
Codex selects medux_word_to_pdf, presents the arguments for review, calls Medux, and reports the response.
Before you start
Authentication
Authentication is required via Authorization header.
Preconditions
Upload the source file and create a file reference before calling this endpoint.
Successful requests return a Medux task record immediately. Use the task query or sync endpoints to track completion.
All file inputs must be uploaded and persisted as file references before submission.
Prompt Codex
Start with a clear instruction that names the Medux operation and the intended inputs.
Convert a Word document (.docx) to PDF.
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
input_file_id
string
Required
Input Word file id.
model_id
string
Optional
Model Default: word-to-pdf-default.
title
string
Optional
Optional task title.
Step-by-step workflow
01
Connect Medux MCP to Codex
Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_word_to_pdf tool is available.
02
Prepare the required inputs
Prepare the source files, asset IDs, text, or settings required by the operation. Upload local media first when the tool requests file IDs.
03
Ask Codex to run Word to PDF
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_word_to_pdf and that each file ID, task ID, option, and output setting matches your request before approving it.
05
Check the Medux response
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.
Workflow recap
User goal
↓
Codex selects medux_word_to_pdf
↓
Review inputs and approve the tool call
↓
Medux runs Word to PDF
↓
Codex reports the response and output
Frequently asked questions
Can Codex use the Medux Word to PDF API through MCP?
Codex can call the medux_word_to_pdf Medux MCP tool to convert a Word document (.docx) to PDF. 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_word_to_pdf. Review its arguments before approval and consult the API reference for the current contract.
Claude-specific workflow
Run Convert DOCX to PDF as a Claude MCP workflow
Keep the goal, source assets, and constraints together in the conversation. Ask Claude to restate the source DOCX file and the desired output name before proposing the Medux document conversion tool. That context checkpoint makes the file roles and desired outcome easy to correct before any Medux call is approved.
Claude prompt pattern
Using the assets and requirements in this conversation, help me convert DOCX to PDF with Medux MCP.
Restate which input fulfills each role: the source DOCX file and the desired output name.
Propose the the Medux document conversion tool call and summarize its arguments before asking for approval.
When it finishes, return the converted PDF with a checklist confirming that the PDF opens, page order is intact, and the document content is readable.
Context checkpoint
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.
Result verification
Keep the Medux task ID in the conversation while Claude checks progress. When processing ends, ask for the converted PDF plus a concise validation checklist confirming that the PDF opens, page order is intact, and the document content is readable.
Before you start
Claude connected to MeduxMake sure the Medux MCP server is available in Claude and the document conversion tools are enabled.
A local source filePlace the DOCX file in a known folder and keep its exact filename ready for the curl upload command.
curl installedThe tutorial uses curl to upload the source document and download the converted PDF.
Tool approvalClaude may ask you to approve Medux tool calls before it creates uploads or starts conversion tasks.
Supported workflow: The same pattern can be used for other document format conversions supported by Medux. Change the source file and requested output format while keeping the upload, task, and download flow.
Step-by-step workflow
01
Open the document conversion workflow
In Claude, open the Medux document conversion tool and describe the result you need. The tutorial starts with a DOCX file and asks Medux to return a PDF.
Use Medux to convert "Artificial Intelligence and Transformer Models.docx" to a PDF file. Upload the file using curl.
Claude receives a plain-language conversion request.
02
Let Claude select the right Medux tool
Claude inspects the available Medux actions and prepares the conversion workflow. Approve the requested tool calls so it can create an upload URL and continue.
Approve only the Medux actions required for upload, conversion, status checks, and result retrieval.
Claude plans the Medux upload and conversion steps.
03
Create an upload URL
Medux returns a temporary upload destination. Claude then prepares a curl command for the source DOCX file. Temporary upload URLs normally expire, so run the command promptly.
curl --request PUT \
--upload-file "./Artificial Intelligence and Transformer Models.docx" \
"<MEDUX_TEMPORARY_UPLOAD_URL>"
Claude displays the temporary upload command.
04
Upload the source document
Run the generated curl command in your terminal. A successful upload makes the DOCX available to the Medux conversion task without manually moving it through another dashboard.
curl --request PUT \
--upload-file "./Artificial Intelligence and Transformer Models.docx" \
"<MEDUX_TEMPORARY_UPLOAD_URL>"
The source file is uploaded from the local terminal.
05
Start the DOCX-to-PDF conversion
Return to Claude after the upload completes. Claude submits the uploaded document to Medux, selects PDF as the target format, and starts the conversion job.
Source format: DOCX
Target format: PDF
Task: Convert the uploaded document
Claude asks Medux to generate the PDF.
06
Wait for the task to finish
Claude checks the Medux task status until the conversion is complete. There is no need to repeatedly download or re-upload the document while the job is running.
Status flow: queued → processing → completed
Claude monitors the conversion task.
07
Download the converted PDF
When Medux returns the output URL, download the PDF with curl. Use -L so redirects are followed, and choose a clear local filename with -o.
curl -L "<MEDUX_OUTPUT_URL>" \
-o "Artificial Intelligence and Transformer Models.pdf"
The completed PDF is downloaded to the local machine.
Workflow at a glance
Prompt Claude
Create upload URL
Upload source file
Convert with Medux
Download output
Ready to use the result
Open the downloaded PDF and verify the layout, text, images, and page count. The conversion is now complete, and the file can be shared, archived, or used in a larger agent workflow.
Explore related workflows
Continue with a nearby Medux workflow or compare how the same task works across Claude MCP and Codex MCP.
Connect either Codex or Claude to Medux MCP, prepare the required inputs, review the proposed medux_word_to_pdf call, and verify the returned result. The tabs above keep client-specific prompting on one canonical page.
Can I use the same Medux tool in Codex and Claude?
Yes. The client interaction differs, but both use the same Medux MCP tool and API request contract shown in this tutorial.
Related developer intent
Use AI agents to convert Word to PDF
This tutorial addresses developer workflows for convert Word to PDF API and convert Word to PDF with Codex MCP by making the task repeatable through the Medux API. Codex or Claude can prepare inputs, show the MCP tool arguments for approval, monitor processing, and return an output that can be checked against the original request.
The same Medux MCP pattern applies to document automation: identify the source file, review the API arguments, monitor any asynchronous work, and validate the converted output.
Can Codex or Claude convert Word to PDF through Medux MCP?
Yes. Use the client-specific tab above to prepare the inputs, review the Medux tool call, run the operation, and verify the returned result. The linked API reference remains the source of truth for supported fields and limits.
Production, trust, and developer intent
Use permissioned document automation to convert Word to PDF
This document conversion API for developers lets Codex or Claude convert Word to PDF while keeping the source file, requested operation, task record, and returned document visible. That makes the MCP workflow easier to review and integrate into a larger application.
For a privacy-conscious document workflow, upload only authorized files, avoid exposing credentials in prompts, restrict result access, and define retention and deletion in the calling system.
How do I keep an MCP document workflow auditable?
Record the approved source file, requested conversion, Medux task ID, returned result, and a final content check before the document moves downstream.
