EAD_Enterprise_Suite_MCP: Command for Claude Code

Signature Lifecycle (EAD Enterprise Suite)

Manage the full digital signature workflow via EAD Enterprise Suite.

Step-by-step path

Use the individual tools when you need custom control over each step.

Key concepts

• Signature types: INTERPOSITION (electronic, placement box) or ADVANCED (qualified, requires a digital certificate from the signer).
• Close condition: ALL_REQUIRED (everyone must sign) or PARTIAL_ALLOWED (first signer closes it).
• Sequence: PARALLEL (all sign simultaneously) or CONFIGURABLE (ordered signing).
• WhatsApp/simple signing link: currently only supported for INTERPOSITION (simple signature). ADVANCED does not currently support WhatsApp delivery.
• Advanced OTP: ADVANCED signatures require phonePrefix and phoneNumber; the signer receives the OTP through that phone channel.
• Document states: DRAFT → processing → READY_TO_SIGN. Must be READY_TO_SIGN before activation.
• Coordinates: Required for all signature types (both INTERPOSITION and ADVANCED). Set before activation via signature_coordinate_set.

IDs you need before starting

• caseFileId — from case_file_list (use the id UUID, not the code like PR82)
• userId — returned by session_info (no parameters needed)

Step 1 — Create the signature request

signature_request_create(
  caseFileId: "<uuid>",
  id: "<new-uuid>",
  name: "My Signature Request",
  language: "es_ES",
  deadline: "2026-06-30T23:59:59.000Z",
  signatureType: "INTERPOSITION",
  closeCondition: "ALL_REQUIRED",
  sequence: "PARALLEL"
)

Returns {} on success (the id you provided becomes the requestId).

Step 2 — Register document

signature_request_add_document(
  caseFileId: "<uuid>",
  requestId: "<sig-request-uuid>",
  id: "<new-uuid>",
  title: "Document Title",
  fileName: "document.pdf",
  fileSize: <bytes>,
  hash: "<sha256-hex>"       # SHA-256 hex digest of the file
)

Returns { url: "<presigned-s3-url>" }. The documentId is the id you passed in this call.