Docupilot for AI agents
Docupilot is a document automation tool that generates PDFs, Word files, contracts, and invoices by connecting to other online services. 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 Docupilot.
Organize documents into folders
Create a folder to keep a batch of generated documents organized by client or project.
Check account details first
Get the authenticated user's account details as a read-only check before running an automation.
List existing folders
List all folders to confirm the right destination exists before filing new documents.
4 Docupilot actions, graded by risk.
Every Docupilot action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- docupilot.get_authenticated_userGet Authenticated User
write
3Create and change things. Allow, or ask the user first.
- docupilot.create_folderCreate Docupilot Folder
- docupilot.folders_listList all folders
- docupilot.folders_createCreate Docupilot Folder
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Docupilot in three steps.
- 01Your users connect DocupilotThey add their Docupilot api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create Docupilot Folder” can wait for the user to approve.
- 03Any agent can actYour agent calls Docupilot through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('docupilot', { read: 'allow', write: 'ask', // create_folder destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Docupilot connects.
Users add their Docupilot 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 Docupilot 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 Docupilot from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Docupilot and Arc0, answered.
Can I use Docupilot with Claude, ChatGPT or Cursor?
Yes. Connect Docupilot 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 Docupilot actions you allow.
How do users connect Docupilot?
Users add their Docupilot 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 Docupilot actions can my agent take?
4 in total: 1 read, 3 write and 0 destructive, such as “create Docupilot Folder”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Docupilot?
Yes. Allow read actions and deny writes in the Docupilot policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Docupilot too?
Yes. The same Docupilot connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Docupilot into your agent.
Your users connect Docupilot once, under your brand. Your agent gets 4 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan