Docmosis for AI agents

Docmosis generates PDF and Word documents from templates by merging in data fields, producing reports, invoices, and letters on demand. 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 + RESTdocmosis.com
AUDIT LOG · DOCMOSISPOLICY: acme-support
09:41:07 · claude · u_8f2read
docmosis.list_images
Docmosis: List Images✓ allowed · 212ms
09:41:08 · claude · u_8f2read
docmosis.ping
Docmosis Ping✓ allowed · 164ms
09:41:09 · claude · u_8f2write
docmosis.environment_ready
Docmosis Environment Ready✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
docmosis.delete_image
Docmosis: Delete Image(s)✕ blocked · policy: deny
EVERY DOCMOSIS CALL, ON THE RECORD
01 · USE CASES

What agents do in Docmosis.

01

List available templates

List the templates in an environment so an agent picks the right one for a document request.

02

Check a template's fields

Read a template's structure to confirm which data fields it expects before rendering.

03

Approve before deleting templates

Require sign-off before deleting a template, since other automations may still depend on it.

02 · ACTIONS

17 Docmosis actions, graded by risk.

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

read

13

Look things up. Allowed by default.

  • docmosis.get_image
    Download Docmosis Images
  • docmosis.get_api_key
    Docmosis: Get API Key
  • docmosis.list_images
    Docmosis: List Images
  • docmosis.get_template
    Download Docmosis Templates
  • docmosis.list_templates
    Docmosis: List Templates
  • docmosis.get_render_tags
    Get Render Tags
  • docmosis.get_sample_data
    Get Template Sample Data
  • docmosis.get_render_queue
    Get Docmosis Render Queue
  • docmosis.get_template_details
    Get Docmosis Template Details
  • docmosis.get_template_structure
    Get Docmosis Template Structure
  • docmosis.get_batch_upload_status
    Get Batch Upload Status
  • docmosis.ping
    Docmosis Ping
  • docmosis.ping_docmosis_service
    Ping Docmosis Service

write

2

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

  • docmosis.environment_ready
    Docmosis Environment Ready
  • docmosis.environment_summary
    Docmosis Environment Summary

destructive

2

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

  • docmosis.delete_image
    Docmosis: Delete Image(s)
  • docmosis.delete_template
    Docmosis: Delete Template(s)
03 · HOW IT WORKS

Docmosis in three steps.

  1. 01Your users connect DocmosisThey add their Docmosis api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “docmosis Environment Ready” can wait for the user, and “docmosis: Delete Image(s)” can be denied outright.
  3. 03Any agent can actYour agent calls Docmosis 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('docmosis', {
  read: 'allow',
  write: 'ask',        // environment_ready
  destructive: 'deny',  // delete_image
})

# 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 Docmosis connects.

Users add their Docmosis 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 Docmosis 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 Docmosis from any agent.

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

Docmosis and Arc0, answered.

Q01

Can I use Docmosis with Claude, ChatGPT or Cursor?

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

Q02

How do users connect Docmosis?

Users add their Docmosis 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 Docmosis actions can my agent take?

17 in total: 13 read, 2 write and 2 destructive, such as “docmosis Environment Ready”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Docmosis?

Yes. Actions like “docmosis: Delete Image(s)” 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 Docmosis too?

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

Get started

Plug Docmosis into your agent.

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

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