Pdfless for AI agents
Pdfless is a document factory for producing PDFs from HTML and CSS templates combined with live data. Development teams use it to automate recurring document generation. 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 Pdfless.
Check available document templates
List document templates read-only to choose the right one for a new PDF batch.
Review a workspace's setup
Look up a workspace's configuration before pointing a new document generation job at it.
Confirm template inventory before cleanup
List templates to identify which ones are outdated before an admin retires them.
2 Pdfless actions, graded by risk.
Every Pdfless action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- pdfless.get_workspaceGet Workspace
- pdfless.list_document_templatesList Document Templates
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Pdfless in three steps.
- 01Your users connect PdflessThey add their Pdfless api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Pdfless through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('pdfless', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Pdfless connects.
Users add their Pdfless 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 Pdfless 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 Pdfless from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Pdfless and Arc0, answered.
Can I use Pdfless with Claude, ChatGPT or Cursor?
Yes. Connect Pdfless 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 Pdfless actions you allow.
How do users connect Pdfless?
Users add their Pdfless 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 Pdfless actions can my agent take?
2 in total: 2 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Pdfless?
Yes. Allow read actions and deny writes in the Pdfless policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Pdfless too?
Yes. The same Pdfless connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Pdfless into your agent.
Your users connect Pdfless once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan