CloudPDF for AI agents
CloudPDF creates, hosts, and securely shares PDF documents, giving a team a way to distribute files without emailing attachments around. 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 CloudPDF.
Look up a shared document
Look up a document's details and access settings before sharing its link with someone.
Update a document's settings
Update a document's sharing settings, such as who can view or download it.
Confirm before deleting a document
Confirm before deleting a hosted document, since its shared link would stop working immediately.
10 CloudPDF actions, graded by risk.
Every CloudPDF action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
5Look things up. Allowed by default.
- cloudpdf.get_accountGet Account
- cloudpdf.get_webhookGet Webhook
- cloudpdf.get_documentGet Document
- cloudpdf.list_webhooksList Webhooks
- cloudpdf.get_document_fileGet Document File
write
3Create and change things. Allow, or ask the user first.
- cloudpdf.create_webhookCreate Webhook
- cloudpdf.update_webhookUpdate Webhook
- cloudpdf.update_documentUpdate Document
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- cloudpdf.delete_webhookDelete Webhook
- cloudpdf.delete_documentDelete Document
CloudPDF in three steps.
- 01Your users connect CloudPDFThey add their CloudPDF api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Webhook” can wait for the user, and “delete Webhook” can be denied outright.
- 03Any agent can actYour agent calls CloudPDF through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('cloudpdf', { read: 'allow', write: 'ask', // create_webhook destructive: 'deny', // delete_webhook }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How CloudPDF connects.
Users add their CloudPDF 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 CloudPDF 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 CloudPDF from any agent.
CloudPDF and Arc0, answered.
Can I use CloudPDF with Claude, ChatGPT or Cursor?
Yes. Connect CloudPDF 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 CloudPDF actions you allow.
How do users connect CloudPDF?
Users add their CloudPDF 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 CloudPDF actions can my agent take?
10 in total: 5 read, 3 write and 2 destructive, such as “create Webhook”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in CloudPDF?
Yes. Actions like “delete Webhook” 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 CloudPDF too?
Yes. The same CloudPDF connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug CloudPDF into your agent.
Your users connect CloudPDF once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan