Unified Codex + Claude tutorial · document

How to convert PowerPoint to PDF with Medux MCP

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

POST/api/app/v1/process/asset/ppt_to_pdf

Convert a PowerPoint (.pptx) file to PDF.

Open the PPT to PDF 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 PowerPoint to PDF as a Codex MCP task

Use the active workspace as the source of truth. Ask Codex to identify the source PowerPoint file ID, select medux_ppt_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_ppt_to_pdf through Medux MCP to convert PowerPoint to PDF.
First inspect and identify the source PowerPoint file ID.
Show me the exact tool arguments before execution.
After the task completes, return the converted PDF and verify that the PDF opens and contains every expected slide in the correct order.

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 and contains every expected slide in the correct order.

What this tutorial does

Medux operation

Convert a PowerPoint (.pptx) file to PDF.

Agent workflow

Codex selects medux_ppt_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 PowerPoint (.pptx) file 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.

FieldTypeRequirementPurpose
input_file_idstringRequiredInput PowerPoint file id.
model_idstringOptionalModel Default: ppt-to-pdf-default.
titlestringOptionalOptional 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_ppt_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 PPT 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_ppt_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_ppt_to_pdf
  ↓
Review inputs and approve the tool call
  ↓
Medux runs PPT to PDF
  ↓
Codex reports the response and output

Frequently asked questions

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

Codex can call the medux_ppt_to_pdf Medux MCP tool to convert a PowerPoint (.pptx) file 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_ppt_to_pdf. Review its arguments before approval and consult the API reference for the current contract.

Claude-specific workflow

Run Convert PowerPoint to PDF as a Claude MCP workflow

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

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 and contains every expected slide in the correct order.

What this tutorial does

Medux operation

Convert a PowerPoint (.pptx) file to PDF.

Agent workflow

Claude selects medux_ppt_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 Claude

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

Convert a PowerPoint (.pptx) file 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.

FieldTypeRequirementPurpose
input_file_idstringRequiredInput PowerPoint file id.
model_idstringOptionalModel Default: ppt-to-pdf-default.
titlestringOptionalOptional task title.

Step-by-step workflow

01

Connect Medux MCP to Claude

Add the Medux remote MCP endpoint to Claude, provide an authorized credential, and confirm that the medux_ppt_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 Claude to run PPT to PDF

Use one direct instruction with the intended values. Claude 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_ppt_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
  ↓
Claude selects medux_ppt_to_pdf
  ↓
Review inputs and approve the tool call
  ↓
Medux runs PPT to PDF
  ↓
Claude reports the response and output

Frequently asked questions

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

Claude can call the medux_ppt_to_pdf Medux MCP tool to convert a PowerPoint (.pptx) file 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_ppt_to_pdf. Review its arguments before approval and consult the API reference for the current contract.

Quick answer

How do I convert PowerPoint to PDF with Medux MCP?

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

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

Upload source files with a presigned URLCheck an asynchronous Medux task
Can Codex or Claude convert PowerPoint 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 PowerPoint to PDF

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

Build with the API

API reference and official examples