Digisign MCP

What davidsimoes/digisign-mcp MCP server does

davidsimoes/digisign-mcp MCP server connects an MCP-compatible client to the DigiSign.cz digital signature API. It lets an assistant inspect account and envelope data, prepare draft envelopes, attach documents, add recipients, place signature fields, and send envelopes for signing.

The server supports a complete envelope workflow. A typical sequence starts by creating a draft, then uploading a PDF or DOCX, adding signers or other recipient types, placing signature tags, and sending the completed envelope. It also supports post-creation operations such as cancelling a sent envelope, deleting a draft, or discarding a draft when the API key does not have delete permission.

How it works

The MCP client calls named tools exposed by the local Node.js process. Read-oriented tools include list_envelopes, get_envelope, list_documents, list_recipients, list_tags, get_download_url, and get_account. These provide envelope status and page filtering, recipient and document details, tag information, temporary download URLs for signed documents, and account usage information.

Write tools change DigiSign data. create_envelope starts a draft, upload_and_attach_document adds a PDF or DOCX, and add_recipient adds a signer, approver, or CC recipient. add_signature_tag supports placeholder-based or coordinate-based placement. send_envelope emails recipients, while the cancellation and deletion tools affect existing envelopes.

For signature placement, placeholders are text markers embedded in a document. DigiSign expects simple ASCII markers using its supported character set; spaces and diacritics are not supported by the documented placeholder pattern. Coordinate placement uses page coordinates in points. The README recommends placeholders because they are less affected by document layout changes, and notes that documentId is required for tag placement.

Setup and configuration

To run davidsimoes/digisign-mcp MCP server, obtain a DigiSign API key pair from the DigiSign dashboard under Settings, developer settings, and API keys. The pair consists of an access key and a secret key.

The repository setup uses Node.js 18 or newer. Clone the project, enter its directory, and run npm install to install dependencies. Register the local entry point with an MCP client by supplying these environment variables:

• DIGISIGN_ACCESS_KEY
• DIGISIGN_SECRET_KEY

The documented registration command targets Claude Code and starts src/index.js with Node.js. The server requires a DigiSign.cz account with API access and an MCP-compatible client.

Tools and capabilities

• List envelopes, optionally filtering by status and page.
• Retrieve envelope status, recipients, and documents.
• List documents, recipients, and signature or form tags.
• Obtain temporary download URLs for signed documents.
• Inspect account credits, plan, and usage.
• Create drafts and attach PDF or DOCX files.
• Add signers, approvers, or CC recipients.
• Add signature fields by placeholder or page coordinates.
• Send, cancel, delete, or discard envelopes.

Limitations and notes

Sending an envelope emails all recipients, and cancelling an envelope notifies signers. Deletion, discarding, and sending are therefore unsuitable for unreviewed automation. The README recommends requiring manual approval or denying these tools in Claude Code settings.

Preparation tools modify draft envelopes even though they do not send them. Treat create_envelope, upload_and_attach_document, add_recipient, and add_signature_tag as write operations when designing permissions.

The material documents Claude Code registration specifically; it does not provide a prebuilt hosted endpoint or a package-manager command that installs davidsimoes/digisign-mcp MCP server directly. The project is licensed under MIT.