PDF Munk for AI agents
PDF Munk provides APIs for generating, converting, editing, and extracting content from PDFs and images. Developers use it for document and image processing pipelines. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in PDF Munk.
Convert images into a PDF
Combine a set of images into a single PDF document for archiving or sharing.
Run OCR on a PDF
Extract readable text from a scanned PDF for search or downstream processing.
Watermark a file
Apply a watermark to a document before it is distributed outside the company.
9 PDF Munk actions, graded by risk.
Every PDF Munk action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- pdf_munk.parse_pdfParse PDF
- pdf_munk.convert_images_to_pdfConvert Images to PDF
- pdf_munk.convert_pdf_to_imagesConvert PDF to Images
write
5Create and change things. Allow, or ask the user first.
- pdf_munk.ocr_pdfOCR PDF
- pdf_munk.ocr_imageOCR Image
- pdf_munk.generate_pdfGenerate PDF
- pdf_munk.generate_imageGenerate Image
- pdf_munk.watermark_fileWatermark File
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- pdf_munk.merge_pdfsMerge PDFs
PDF Munk in three steps.
- 01Your users connect PDF MunkThey add their PDF Munk api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “oCR PDF” can wait for the user, and “merge PDFs” can be denied outright.
- 03Any agent can actYour agent calls PDF Munk through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('pdf_munk', { read: 'allow', write: 'ask', // ocr_pdf destructive: 'deny', // merge_pdfs }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How PDF Munk connects.
Users add their PDF Munk api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same PDF Munk connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use PDF Munk from any agent.
PDF Munk and Arc0, answered.
Can I use PDF Munk with Claude, ChatGPT or Cursor?
Yes. Connect PDF Munk to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the PDF Munk actions you allow.
How do users connect PDF Munk?
Users add their PDF Munk api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which PDF Munk actions can my agent take?
9 in total: 3 read, 5 write and 1 destructive, such as “oCR PDF”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in PDF Munk?
Yes. Actions like “merge PDFs” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call PDF Munk too?
Yes. The same PDF Munk connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug PDF Munk into your agent.
Your users connect PDF Munk once, under your brand. Your agent gets 9 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan