Text to PDF for AI agents
Text to PDF converts plain text into a PDF file, a small utility for turning notes, logs, or generated text into a document that can be shared or archived. 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 Text to PDF.
Convert text to a PDF
Turn a block of text into a downloadable PDF file.
Download a converted file
Retrieve the finished PDF after a conversion job completes, a read-only fetch.
Confirm before deleting a file
Check with the user before deleting a converted file from storage, since it can't be recovered afterward.
6 Text to PDF actions, graded by risk.
Every Text to PDF 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.
- text_to_pdf.download_fileDownload File
- text_to_pdf.convert_text_to_pdfConvert Text to PDF
write
2Create and change things. Allow, or ask the user first.
- text_to_pdf.upload_fileUpload File to ConvertAPI
- text_to_pdf.start_async_conversionStart Async Conversion
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- text_to_pdf.delete_fileDelete File
- text_to_pdf.delete_async_jobDelete Async Job
Text to PDF in three steps.
- 01Your users connect Text to PDFThey add their Text to PDF no auth on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “upload File to ConvertAPI” can wait for the user, and “delete File” can be denied outright.
- 03Any agent can actYour agent calls Text to PDF through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('text_to_pdf', { read: 'allow', write: 'ask', // upload_file destructive: 'deny', // delete_file }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Text to PDF connects.
Text to PDF needs no credentials. Arc0 still applies your policies and records every call, so public tools get the same controls as private ones.
The same Text to PDF 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
- No auth
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Text to PDF from any agent.
Text to PDF and Arc0, answered.
Can I use Text to PDF with Claude, ChatGPT or Cursor?
Yes. Connect Text to PDF 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 Text to PDF actions you allow.
How do users connect Text to PDF?
Text to PDF needs no credentials. Arc0 still applies your policies and records every call, so public tools get the same controls as private ones.
Which Text to PDF actions can my agent take?
6 in total: 2 read, 2 write and 2 destructive, such as “upload File to ConvertAPI”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Text to PDF?
Yes. Actions like “delete File” 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 Text to PDF too?
Yes. The same Text to PDF connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Text to PDF into your agent.
Your users connect Text to PDF once, under your brand. Your agent gets 6 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan