iLovePDF for AI agents
iLovePDF processes, converts, and optimizes PDF and image files, covering tasks like merging, splitting, and compressing documents. Office and operations staff use it to keep documents moving without manual reformatting. 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 iLovePDF.
Merge PDFs into one file
Merge a set of uploaded PDF files into a single document for a client packet.
Compress a large PDF
Compress an oversized PDF so it can be attached to an email without bouncing.
Check a conversion task's status
Poll a submitted PDF conversion task to see when the output file is ready.
9 iLovePDF actions, graded by risk.
Every iLovePDF action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
4Look things up. Allowed by default.
- ilovepdf.get_task_statusGet Task Status
- ilovepdf.get_account_infoGet Account Info
- ilovepdf.convert_images_to_pdfConvert Images to PDF
- ilovepdf.convert_pdf_to_imagesConvert PDF to Images
write
3Create and change things. Allow, or ask the user first.
- ilovepdf.split_pdfSplit PDF
- ilovepdf.compress_pdfsCompress PDFs
- ilovepdf.compress_imagesCompress Images
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- ilovepdf.delete_taskDelete Task
- ilovepdf.merge_pdfsMerge PDFs
iLovePDF in three steps.
- 01Your users connect iLovePDFThey add their iLovePDF api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “split PDF” can wait for the user, and “delete Task” can be denied outright.
- 03Any agent can actYour agent calls iLovePDF through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('ilovepdf', { read: 'allow', write: 'ask', // split_pdf destructive: 'deny', // delete_task }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How iLovePDF connects.
Users add their iLovePDF 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 iLovePDF 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 iLovePDF from any agent.
iLovePDF and Arc0, answered.
Can I use iLovePDF with Claude, ChatGPT or Cursor?
Yes. Connect iLovePDF 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 iLovePDF actions you allow.
How do users connect iLovePDF?
Users add their iLovePDF 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 iLovePDF actions can my agent take?
9 in total: 4 read, 3 write and 2 destructive, such as “split PDF”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in iLovePDF?
Yes. Actions like “delete Task” 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 iLovePDF too?
Yes. The same iLovePDF connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug iLovePDF into your agent.
Your users connect iLovePDF 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