

Process Document Files with Codex and pdfAssistant
An agent can help organize a document task, but a directory name is not itself a remote upload. Codex handles local work through its available environment; pdfAssistant performs supported operations on files made available to the MCP server.
Connect the server, test one file and specify the output directory and review requirements. Expand to multiple files only after the upload and returned-file path work in your environment.
Start with the result you need
Connect and authenticate
Follow the Codex integration guide and confirm that the pdfAssistant tools are available.
Prepare a small fictional folder
Use distinct names such as scan-01.pdf and scan-02.pdf. Keep originals in an inputs directory and outputs separate.
Run and review one operation
Ask Codex to arrange the supported upload, process the sample and save the returned output where its environment permits. Check the output before processing the remaining files.
Use pdfAssistant to make inputs/scan-01.pdf searchable while preserving its page images. Use the supported file upload flow; do not assume the remote server can read a local path. Save the returned output to outputs/scan-01-searchable.pdf if the local environment allows it. Report warnings, keep the original unchanged and stop after this one file for review.What to look for in the result
| Local role | Remote role |
|---|---|
| Codex can inspect an allowed local directory. | pdfAssistant needs the file through a supported upload route. |
| Codex can save a returned output where permitted. | pdfAssistant returns the processed file or its resource metadata. |
| The local environment has its own approvals. | The MCP connection has separate account and tool access. |
Review before you move on
- Confirm which file was uploaded and which file was returned.
- Compare page count, recognized text and source-image appearance.
- Read any warning before expanding the run.
- Keep deletion, overwriting and sensitive edits behind explicit task instructions.
Questions before you start
Where are the setup commands?
Use the Codex integration page for the current server registration and OAuth login commands.
Can I automate the whole folder immediately?
First verify a representative file and the output path. Then specify the scope, naming rules and handling of failures before expanding the job.

