Get started

DocuSeal for AI agents

DocuSeal is an e-signature platform with an API for building signing workflows, letting teams automate document and template management instead of relying on a manual web interface. 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.

Connect DocuSealSee the 22 actions ↓
DocumentsAPI keyMCP + RESTdocuseal.com
AUDIT LOG · DOCUSEALPOLICY: acme-support
09:41:07 · claude · u_8f2read
docuseal.list_submitters
List Submitters✓ allowed · 212ms
09:41:08 · claude · u_8f2read
docuseal.get_template
Get Template✓ allowed · 164ms
09:41:09 · claude · u_8f2write
docuseal.create_submission
Create Submission✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
docuseal.archive_template
Archive Template✕ blocked · policy: deny
EVERY DOCUSEAL CALL, ON THE RECORD
01 · USE CASES

What agents do in DocuSeal.

01

Create a submission for signature

Create a submission from a template and send it to the named signers for their signature.

02

Check a submission's status

Get a submission's current state to tell a customer whether all parties have signed yet.

03

Confirm before archiving a template

Require approval before archiving a template, since it can affect submissions still in progress.

02 · ACTIONS

22 DocuSeal actions, graded by risk.

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

read

7

Look things up. Allowed by default.

  • docuseal.get_template
    Get Template
  • docuseal.get_submitter
    Get Submitter
  • docuseal.get_submission
    Get Submission
  • docuseal.list_submitters
    List Submitters
  • docuseal.list_templates2
    List Templates (Enhanced)
  • docuseal.list_submissions
    List Submissions
  • docuseal.get_submission_documents
    Get Submission Documents

write

12

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

  • docuseal.update_submitter
    Update Submitter
  • docuseal.update_template2
    Update Template
  • docuseal.create_submission
    Create Submission
  • docuseal.create_template_from_pdf
    Create Template From PDF
  • docuseal.create_template_from_docx
    Create Template from DOCX
  • docuseal.update_template_documents
    Update Template Documents
  • docuseal.create_submission_from_pdf
    Create Submission From PDF
  • docuseal.create_template_from_html2
    Create Template from HTML
  • docuseal.create_submission_from_docx
    Create Submission From DOCX
  • docuseal.create_submission_from_html
    Create Submission From HTML
  • docuseal.create_submissions_from_emails
    Create Submissions From Emails
  • docuseal.clone_template2
    Clone Template (v2)

destructive

3

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

  • docuseal.archive_template
    Archive Template
  • docuseal.archive_submission
    Archive Submission
  • docuseal.merge_templates
    Merge Templates
03 · HOW IT WORKS

DocuSeal in three steps.

  1. 01Your users connect DocuSealThey add their DocuSeal api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Submission” can wait for the user, and “archive Template” can be denied outright.
  3. 03Any agent can actYour agent calls DocuSeal 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('docuseal', {
  read: 'allow',
  write: 'ask',        // create_submission
  destructive: 'deny',  // archive_template
})

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

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

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More documents apps.

Google Docs43 actionsActiveMerge13 actionsAirparser10 actionsAlgodocs3 actionsDocuSign338 actionsSharePoint Graph162 actionsSharePoint105 actionsDocumenso77 actions
ALL DOCUMENTS APPS →
07 · FAQ

DocuSeal and Arc0, answered.

Q01

Can I use DocuSeal with Claude, ChatGPT or Cursor?

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

Q02

How do users connect DocuSeal?

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

22 in total: 7 read, 12 write and 3 destructive, such as “create Submission”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in DocuSeal?

Yes. Actions like “archive Template” 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 DocuSeal too?

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

Get started

Plug DocuSeal into your agent.

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

Connect DocuSealBrowse all apps →

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