Purpose
digisign-mcp is an MCP (Model Context Protocol) server for integrating with the DigiSign.cz digital signature API. It is built specifically for Claude Code, allowing users to create, send, and manage digital signature envelopes directly in the AI coding assistant.
Main Capabilities
The server provides two types of tools:
- Read tools: Can be safely auto-approved.
- Write tools: Manual approval is recommended to avoid accidental operations.
The specific tools include:
create_envelope: Create a draft envelope.upload_and_attach_document: Upload and attach a PDF document.add_recipient: Add a signer (a mobile number is required when using SMS authentication).add_signature_tag: Place a signature tag.send_envelope: Send the envelope for signing.
In addition, operations for canceling and deleting envelopes are also involved (the specific tool names are not listed in the materials).
How to Use
1. Obtain a DigiSign API Key
In the DigiSign dashboard: Settings > Pro vyvojare > API klice. Create an API key pair (access key + secret key).
2. Install Dependencies
The materials do not provide specific installation commands.
3. Register with Claude Code
The materials do not provide specific registration commands.
Security Recommendations
In ~/.claude/settings.local.json , add the irreversible write tools to the deny list to ensure that Claude Code prompts for confirmation before sending, canceling, or deleting an envelope.
The safe preparation tools (create_envelope、upload_and_attach_document、add_recipient、add_signature_tag) can be added to the allow list because they only modify draft envelopes.
Signature Tag Positioning
There are two methods for placing signature tags on a document:
Placeholder-based (recommended)
Add invisible text markers in the document (for example, white text such as {sign_here}). DigiSign will find them in the PDF text layer and position the signature tags relative to them.
Important note: DigiSign's placeholder regular expression only allows [\w\-\{\}\[\]\(\)=,]—spaces or diacritics are not allowed. Use simple ASCII placeholders, such as {sign_ceo}、{sign_client}.
Positioning:bottom_left places the signature box above the placeholder text (the standard practice for contracts, with the signature above the printed name).scale: 70 keeps the box compact.
Note: Even when using placeholder positioning,documentId is still required.
Coordinate-based
Place tags at exact page coordinates (in points). The materials do not provide specific examples.
The placeholder-based method is more robust—it adapts to document layout changes.
Typical Workflow
create_envelope— Create a draftupload_and_attach_document— Attach a PDFadd_recipient— Add a signer (a mobile number is required when using SMS authentication)add_signature_tag— Place a signature tagsend_envelope— Send for signing
Use Cases
Suitable for developers and teams that need to integrate DigiSign.cz digital signature functionality into an AI coding assistant (such as Claude Code), for automating the creation, sending, and management of digital signature envelopes.
Limitations
- Requires a DigiSign.cz account with API access.
- Requires Claude Code or any MCP-compatible client.
- Placeholder regular expression restriction: spaces or diacritics are not allowed.
- The materials do not provide specific installation commands and registration commands.
- The materials do not provide specific examples of coordinate-based positioning.
Author
Built by David Simoes / Sounds Good Agency.