Docugenerate for AI agents

DocuGenerate converts Word templates and JSON data into PDF documents, automating contracts, invoices, letters, and certificates for teams that generate the same document type repeatedly. 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.

DocumentsAPI keyMCP + RESTdocugenerate.com
AUDIT LOG · DOCUGENERATEPOLICY: acme-support
09:41:07 · claude · u_8f2read
docugenerate.list_documents
List documents by template✓ allowed · 212ms
09:41:08 · claude · u_8f2read
docugenerate.get_document
Get document by ID✓ allowed · 164ms
09:41:09 · claude · u_8f2write
docugenerate.document_update
Update Document✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
docugenerate.delete_document
Delete Document✕ blocked · policy: deny
EVERY DOCUGENERATE CALL, ON THE RECORD
01 · USE CASES

What agents do in Docugenerate.

01

Generate a document from a template

Generate a contract or invoice from a template using the customer data supplied for that record.

02

Look up a template by ID

Get a template's details to confirm its fields match the data being sent before generating.

03

Confirm before deleting a template

Require sign-off before deleting a template, since other scheduled generations may still reference it.

02 · ACTIONS

9 Docugenerate actions, graded by risk.

Every Docugenerate action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

3

Look things up. Allowed by default.

  • docugenerate.get_document
    Get document by ID
  • docugenerate.get_template
    Get template by ID
  • docugenerate.list_documents
    List documents by template

write

4

Create and change things. Allow, or ask the user first.

  • docugenerate.document_update
    Update Document
  • docugenerate.template_update
    Update Template
  • docugenerate.document_generate
    Generate documents from template
  • docugenerate.template_get_or_list
    Get or list templates

destructive

2

Delete, cancel or archive. Ask first, or deny outright.

  • docugenerate.delete_document
    Delete Document
  • docugenerate.delete_template
    Delete template
03 · HOW IT WORKS

Docugenerate in three steps.

  1. 01Your users connect DocugenerateThey add their Docugenerate api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “update Document” can wait for the user, and “delete Document” can be denied outright.
  3. 03Any agent can actYour agent calls Docugenerate through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('docugenerate', {
  read: 'allow',
  write: 'ask',        // document_update
  destructive: 'deny',  // delete_document
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Docugenerate connects.

Users add their Docugenerate 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 Docugenerate 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
05 · WORKS WITH

Use Docugenerate from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Docugenerate and Arc0, answered.

Q01

Can I use Docugenerate with Claude, ChatGPT or Cursor?

Yes. Connect Docugenerate 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 Docugenerate actions you allow.

Q02

How do users connect Docugenerate?

Users add their Docugenerate 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.

Q03

Which Docugenerate actions can my agent take?

9 in total: 3 read, 4 write and 2 destructive, such as “update Document”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Docugenerate?

Yes. Actions like “delete Document” 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.

Q05

Can my own backend call Docugenerate too?

Yes. The same Docugenerate connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Docugenerate into your agent.

Your users connect Docugenerate once, under your brand. Your agent gets 9 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan