digisign-mcp
The digisign-mcp server enables AI assistants like Claude Code to create, manage, and send digital signature envelopes via the DigiSign.cz API.
Read/Query capabilities:
List envelopes — browse with optional filters by status (draft, sent, completed, expired, declined, cancelled) and pagination
Get envelope details — retrieve full info on a specific envelope
List documents/recipients/tags — view attachments, recipient signing statuses, and placed signature tags
Get download URL — obtain a temporary (5-min) link for signed documents from completed envelopes
Get account info — check credits, plan, and usage
Write/Action capabilities:
Create envelope — start a new draft with custom name, email body, and sender details
Upload & attach document — upload a local PDF or DOCX file to an envelope
Add recipient — add signers, approvers, in-person signers, or CC recipients (with optional SMS auth)
Add signature tag — place signature, approval, text, date, or checkbox tags using placeholder-based or coordinate-based positioning
Send envelope — dispatch a draft to all recipients for signing
Cancel envelope — cancel a sent envelope (signers are notified)
Delete/Discard envelope — permanently delete or discard a draft envelope
Safety controls: Permissions can be configured to require manual approval for irreversible actions like sending or canceling envelopes.
DigiSign MCP Server
MCP server for the DigiSign.cz digital signature API. Built for Claude Code.
Create, send, and manage digital signature envelopes directly from your AI coding assistant.
Setup
1. Get DigiSign API keys
In your DigiSign dashboard: Settings > Pro vyvojare > API klice. Create an API key pair (access key + secret key).
2. Install dependencies
git clone https://github.com/davidsimoes/digisign-mcp.git
cd digisign-mcp
npm install3. Register with Claude Code
claude mcp add digisign \
-e DIGISIGN_ACCESS_KEY=your_access_key \
-e DIGISIGN_SECRET_KEY=your_secret_key \
-- node /path/to/digisign-mcp/src/index.jsRelated MCP server: mcp-dropbox-sign
Tools
Read tools (safe to auto-approve)
Tool | Description |
| List envelopes with optional status/page filters |
| Get detailed envelope info (status, recipients, documents) |
| List documents attached to an envelope |
| List recipients and their signing status |
| List signature/form tags placed on documents |
| Get temporary download URL for signed documents |
| Get account info (credits, plan, usage) |
Write tools (recommend manual approval)
Tool | Description |
| Create a new draft envelope |
| Upload a PDF/DOCX and attach to an envelope |
| Add a signer, approver, or CC recipient |
| Place signature/form tag (placeholder or coordinate positioning) |
| Send envelope for signing (emails all recipients) |
| Cancel a sent envelope (notifies signers) |
| Delete a draft envelope |
| Discard a draft envelope (use when API key lacks delete permission) |
Safety recommendations
Add irreversible write tools to your deny list in ~/.claude/settings.local.json:
{
"permissions": {
"deny": [
"mcp__digisign__send_envelope",
"mcp__digisign__cancel_envelope",
"mcp__digisign__delete_envelope",
"mcp__digisign__discard_envelope"
]
}
}This ensures Claude Code prompts for confirmation before sending, cancelling, or deleting envelopes.
Safe preparation tools (create_envelope, upload_and_attach_document, add_recipient, add_signature_tag) can be added to the allow list since they only modify draft envelopes.
Signature tag positioning
Two approaches for placing signature tags on documents:
Placeholder-based (recommended)
Add invisible text markers in your document (e.g., white-colored text like {sign_here}). DigiSign finds them in the PDF text layer and positions the signature tag relative to them.
add_signature_tag(
envelopeId: "...",
recipientId: "...",
documentId: "...",
placeholder: "{sign_here}",
positioning: "bottom_left",
scale: 70
)Important: DigiSign's placeholder regex only allows [\w\-\{\}\[\]\(\)=,] — no spaces or diacritics. Use simple ASCII placeholders like {sign_ceo}, {sign_client}.
Positioning: bottom_left places the signature box above the placeholder text (standard for contracts where the signature goes above the printed name). scale: 70 keeps the box compact.
Note: documentId is required even when using placeholder positioning.
Coordinate-based
Places tag at exact page coordinates (in points):
add_signature_tag(
envelopeId: "...",
recipientId: "...",
documentId: "...",
page: 5,
xPosition: 320,
yPosition: 680
)Placeholder-based is more robust — it survives document layout changes.
Typical workflow
create_envelope— create a draftupload_and_attach_document— attach the PDFadd_recipient— add signers (mobile number required for SMS auth)add_signature_tag— place signature tagssend_envelope— send for signing
Requirements
Node.js 18+
DigiSign.cz account with API access
Claude Code (or any MCP-compatible client)
License
MIT
Built by David Simoes / Sounds Good Agency
Available Tools
15 toolsadd_recipientC
Add a signer, approver, or CC recipient to an envelope.
Inputs: envelopeId (required), role (required), name (required), email (required), +1 more.
add_signature_tagB
Place a signature or form tag on a document. Use placeholder for text-based positioning or coordinates for exact placement.
Inputs: envelopeId (required), recipientId (required), documentId, type, +6 more.
cancel_envelopeC
Cancel a sent envelope. Signers will be notified.
Inputs: envelopeId (required).
create_envelopeA
Create a new draft envelope for digital signature. Returns envelope ID for subsequent operations.
Inputs: name (required), emailBody, emailBodyCompleted, senderName, +1 more.
delete_envelopeA
Delete a draft envelope. Cannot delete sent/completed envelopes.
Inputs: envelopeId (required).
discard_envelopeA
Discard a draft envelope. Moves it to discarded state. Use this instead of delete when the API key lacks ROLE_ENVELOPE_DELETE.
Inputs: envelopeId (required).
get_accountB
Get DigiSign account info — credits, plan, usage.
Inputs: no named parameters.
get_download_urlA
Get a temporary download URL (valid 5 min) for signed documents from a completed envelope.
Inputs: envelopeId (required), output.
get_envelopeB
Get detailed information about a specific envelope including status, recipients, documents.
Inputs: envelopeId (required).
list_documentsC
List documents attached to an envelope.
Inputs: envelopeId (required).
list_envelopesB
List envelopes with optional status filter. Returns envelope IDs, names, and statuses.
Inputs: status, page, itemsPerPage.
list_recipientsC
List recipients of an envelope with their signing status.
Inputs: envelopeId (required).
list_tagsC
List signature/form tags on an envelope.
Inputs: envelopeId (required).
send_envelopeB
Send a draft envelope for signature. Requires at least one document, one signer, and signature tags placed.
Inputs: envelopeId (required).
upload_and_attach_documentC
Upload a local file (PDF/DOCX) and attach it to an envelope.
Inputs: envelopeId (required), filePath (required), documentName.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 15 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, 'add_recipient' and 'list_recipients' are complementary but non-overlapping, while 'delete_envelope' and 'discard_envelope' are explicitly differentiated by permissions and state handling. The descriptions clearly delineate each tool's specific function within the envelope lifecycle.
All tools follow a consistent verb_noun naming pattern throughout, such as 'create_envelope', 'list_envelopes', and 'upload_and_attach_document'. The naming is uniform, predictable, and enhances readability, making it easy for agents to understand and select the appropriate tool for each operation.
With 15 tools, the server is well-scoped for digital signature management, covering the full envelope lifecycle from creation to completion. Each tool earns its place by addressing specific needs like recipient management, document handling, and status tracking, without being overly sparse or bloated.
The tool set provides complete CRUD/lifecycle coverage for the digital signature domain. It includes envelope creation, management (send, cancel, delete/discard), recipient and document handling, status retrieval, and download capabilities, with no obvious gaps that would cause agent failures in typical workflows.
Maintenance
Related MCP Connectors
MCP server for the PDFGate API. Generate PDFs, manage documents and handle e-signatures.
PandaDoc MCP server for creating, sending, signing, and tracking PandaDoc documents.
MCP server for ABRA Flexi — accounting, contacts, stock and draft-checked invoice creation.
Hosted MCP server for Dropbox Sign — signature requests, templates, and account for AI agents.
Related MCP Servers
AlicenseAqualityFmaintenancehttps://github.com/signnow/sn-mcp-server MCP server for SignNow e-signature: templates, invites, embedded signing/editor, status & downloads.258MIT- AlicenseNot gradedqualityCmaintenanceMCP server for the Dropbox Sign API supporting signature requests, templates, teams, accounts, events, documents, signers, reports, bulk operations, and workflows.MIT
- AlicenseCqualityDmaintenanceMCP server for the EZD PUW electronic document management system of Polish public administration, providing 91 tools covering the full API for documents, cases, correspondence, ePUAP, eDelivery, blockchain, and more.91MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for accessing Czech datové schránky (ISDS) with legal semantics. Enables AI agents to safely read, send, and archive messages while respecting delivery triggers and deadlines.3MIT