Can I convert PDF to DOCX with both Codex and Claude?

Yes. Codex and Claude can use medux_pdf_to_docx through Medux MCP. Choose the matching tab for client-specific prompting while using the same Medux operation and request contract.

Which Medux MCP tool does this tutorial use?

This workflow uses medux_pdf_to_docx. Review the linked API reference for the current request and response contract.

Unified Codex + Claude tutorial · document

How to convert PDF to DOCX with Medux MCP

Learn to convert PDF to DOCX with the Medux API through Codex or Claude MCP. Check inputs, tool calls, task status, and output.

POST/api/app/v1/process/asset/pdf_to_docx

Convert a PDF to a DOCX file.

Open the PDF to DOCX API reference →

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 PDF to DOCX as a Codex MCP task

Use the active workspace as the source of truth. Ask Codex to identify the source PDF file ID, select medux_pdf_to_docx, 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_pdf_to_docx through Medux MCP to convert PDF to DOCX.
First inspect and identify the source PDF file ID.
Show me the exact tool arguments before execution.
After the task completes, return the converted DOCX file and verify that the DOCX opens and preserves the expected text, tables, and page sequence.

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 DOCX file. The final check is explicit: confirm that the DOCX opens and preserves the expected text, tables, and page sequence.

What this tutorial does

Medux operation

Convert a PDF to a DOCX file.

Agent workflow

Codex selects medux_pdf_to_docx, 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 PDF to a DOCX file.

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 PDF file id.
`model_id`	string	Optional	Model Default: pdf-to-docx-default.
`title`	string	Optional	Optional task title.

Step-by-step workflow

Connect Medux MCP to Codex

Add the Medux remote MCP endpoint to Codex, provide an authorized credential, and confirm that the medux_pdf_to_docx tool is available.

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.

Ask Codex to run PDF to DOCX

Use one direct instruction with the intended values. Codex should select the Medux tool and show the proposed arguments before execution.

Review and approve the tool call

Check that the tool is medux_pdf_to_docx and that each file ID, task ID, option, and output setting matches your request before approving it.

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_pdf_to_docx
  ↓
Review inputs and approve the tool call
  ↓
Medux runs PDF to DOCX
  ↓
Codex reports the response and output

Frequently asked questions

Can Codex use the Medux PDF to DOCX API through MCP?

Codex can call the medux_pdf_to_docx Medux MCP tool to convert a PDF to a DOCX file. 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_pdf_to_docx. Review its arguments before approval and consult the API reference for the current contract.

Claude-specific workflow

Run Convert PDF to DOCX as a Claude MCP workflow

Keep the goal, source assets, and constraints together in the conversation. Ask Claude to restate the source PDF file ID before proposing medux_pdf_to_docx. 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 PDF to DOCX with Medux MCP.
Restate which input fulfills each role: the source PDF file ID.
Propose the medux_pdf_to_docx call and summarize its arguments before asking for approval.
When it finishes, return the converted DOCX file with a checklist confirming that the DOCX opens and preserves the expected text, tables, and page sequence.

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 DOCX file plus a concise validation checklist confirming that the DOCX opens and preserves the expected text, tables, and page sequence.

What this tutorial does

Medux operation

Convert a PDF to a DOCX file.

Agent workflow

Claude selects medux_pdf_to_docx, 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 Claude

Start with a clear instruction that names the Medux operation and the intended inputs.

Convert a PDF to a DOCX file.

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 PDF file id.
`model_id`	string	Optional	Model Default: pdf-to-docx-default.
`title`	string	Optional	Optional task title.

Step-by-step workflow

Connect Medux MCP to Claude

Add the Medux remote MCP endpoint to Claude, provide an authorized credential, and confirm that the medux_pdf_to_docx tool is available.

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.

Ask Claude to run PDF to DOCX

Use one direct instruction with the intended values. Claude should select the Medux tool and show the proposed arguments before execution.

Review and approve the tool call

Check that the tool is medux_pdf_to_docx and that each file ID, task ID, option, and output setting matches your request before approving it.

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
  ↓
Claude selects medux_pdf_to_docx
  ↓
Review inputs and approve the tool call
  ↓
Medux runs PDF to DOCX
  ↓
Claude reports the response and output

Frequently asked questions

Can Claude use the Medux PDF to DOCX API through MCP?

Claude can call the medux_pdf_to_docx Medux MCP tool to convert a PDF to a DOCX file. 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_pdf_to_docx. Review its arguments before approval and consult the API reference for the current contract.

Quick answer

How do I convert PDF to DOCX with Medux MCP?

Connect either Codex or Claude to Medux MCP, prepare the required inputs, review the proposed medux_pdf_to_docx 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 PDF to DOCX

This tutorial addresses developer workflows for convert PDF to DOCX API and convert PDF to DOCX 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.

Upload source files with a presigned URL Check an asynchronous Medux task

Can Codex or Claude convert PDF to DOCX 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 PDF to DOCX

This document conversion API for developers lets Codex or Claude convert PDF to DOCX 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.

Build with the API

API reference and official examples

PDF to DOCX API referenceCurrent request fields, response data, limits, and examples.
Official Codex workflow exampleClient-specific prompt, approval, and result-verification example.
Official Claude workflow exampleClient-specific prompt, approval, and result-verification example.