mcpField
D
docuseal-cli

docuseal-cli

github.com/docusealcoDocuments9216 installsUpdated 4w ago
Repository

About docuseal-cli

docuseal-cli is a command-line skill for managing DocuSeal templates, submissions, and submitters through its API. It requires explicit flags, accepts structured body data, and returns JSON output.

Key features

  1. 01Manage templates and documents
  2. 02Create and track submissions
  3. 03List and update submitters
  4. 04JSON output and structured parameters
  5. 05Environment-variable authentication

Use cases

  1. 01Create a template from a PDF
  2. 02Send signing requests to recipients
  3. 03Check pending signing status

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/docusealco/docuseal-agent-skills --skill docuseal-cli

After installing, type/docuseal-cliin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
docx-variables.md
field-tags.md
html-fields.md
submissions.md
submitters.md
templates.md

Details

From the project README

Agent Protocol

Rules for agents:

  • Supply ALL required flags — the CLI will not prompt for missing parameters.
  • Output is always JSON.
  • Use -d key=value (bracket notation) or -d '{"..": ".."}' (JSON) for body and array parameters.

Authentication

Set environment variables:

  • DOCUSEAL_API_KEY — API key (required). Get yours at https://console.docuseal.com/api
  • DOCUSEAL_SERVER — global (default), europe, or full URL for self-hosted (e.g. https://docuseal.yourdomain.com)

Available Commands

Command GroupWhat it does
templateslist, retrieve, update, archive, create-pdf, create-docx, create-html, clone, merge, update-documents
submissionslist, retrieve, update, archive, create, send-emails, create-pdf, create-docx, create-html, documents
submitterslist, retrieve, update

Read the matching reference file for detailed flags and examples.

Common Mistakes

#MistakeFix
1Forgetting -d template_id=<id> on submissions create--template-id is a flag; submitters and other body params go via -d
2Passing a plain file path as a URL--file accepts a local path; for remote files use -d "documents[0][file]=https://..."
3Expecting array params as comma-separatedArrays use bracket notation: -d "template_ids[]=1" -d "template_ids[]=2"
4Using templates create-pdf without a Pro planCommands marked (Pro) require a DocuSeal Pro subscription
5Sending to multiple recipients with submissions createUse submissions send-emails --emails [email protected],[email protected] for bulk; submissions create is per-submitter

Security

The CLI accepts user-provided file paths, remote URLs (documents[0][file]=https://...), and HTML content as template input. This is by design — all content originates from the authenticated user and is sent directly to the DocuSeal API over HTTPS. The CLI does not fetch, render, or execute remote content locally; it passes references to the server for processing. No user input is interpolated into shell commands.

Common Patterns

List templates:

docuseal templates list --q "NDA" --limit 20

Create a template from a PDF and send for signing:

docuseal templates create-pdf --file contract.pdf --name "NDA"
docuseal submissions send-emails --template-id 1001 --emails [email protected]

Create a submission with pre-filled fields (bracket notation):

docuseal submissions create --template-id 1001 \
  -d "submitters[0][email][email protected]" \
  -d "submitters[0][values][Company Name]=Acme Corp"

Create a submission with pre-filled fields (JSON):

docuseal submissions create --template-id 1001 \
  -d '{"submitters": [{"email": "[email protected]", "values": {"Company Name": "Acme Corp"}}]}'

Check signing status:

docuseal submissions list --template-id 1001 --status pending

Update a submitter:

docuseal submitters update 201 --email [email protected] --send-email

When to Load References

Comments

Markdown supported