DocuPotion for AI agents
DocuPotion generates PDF and PNG documents from reusable templates, turning structured data into finished files automatically for teams that need consistent output without manual formatting work. 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 DocuPotion.
Generate a document from a template
Create a PDF from a chosen template using the data supplied for that record.
List available templates
List templates on the account so an agent can pick the correct one for a request.
Check account status read-only
Read account details as a check before running a generation job that consumes credits.
3 DocuPotion actions, graded by risk.
Every DocuPotion 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.
- docupotion.get_accountGet Account
- docupotion.list_templatesList Templates
write
1Create and change things. Allow, or ask the user first.
- docupotion.create_documentCreate Document
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
DocuPotion in three steps.
- 01Your users connect DocuPotionThey add their DocuPotion api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create Document” can wait for the user to approve.
- 03Any agent can actYour agent calls DocuPotion through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('docupotion', { read: 'allow', write: 'ask', // create_document destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How DocuPotion connects.
Users add their DocuPotion 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 DocuPotion 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 DocuPotion from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
DocuPotion and Arc0, answered.
Can I use DocuPotion with Claude, ChatGPT or Cursor?
Yes. Connect DocuPotion 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 DocuPotion actions you allow.
How do users connect DocuPotion?
Users add their DocuPotion 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 DocuPotion actions can my agent take?
3 in total: 2 read, 1 write and 0 destructive, such as “create Document”. Your policies decide which of them each agent may call.
Can I make my agent read-only in DocuPotion?
Yes. Allow read actions and deny writes in the DocuPotion policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call DocuPotion too?
Yes. The same DocuPotion connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug DocuPotion into your agent.
Your users connect DocuPotion once, under your brand. Your agent gets 3 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan