digisign-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DIGISIGN_ACCESS_KEY | Yes | Your DigiSign API access key found in Settings > Pro vyvojare > API klice. | |
| DIGISIGN_SECRET_KEY | Yes | Your DigiSign API secret key found in Settings > Pro vyvojare > API klice. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_envelopesB | List envelopes with optional status filter. Returns envelope IDs, names, and statuses. |
| get_envelopeB | Get detailed information about a specific envelope including status, recipients, documents. |
| list_documentsC | List documents attached to an envelope. |
| list_recipientsC | List recipients of an envelope with their signing status. |
| list_tagsC | List signature/form tags on an envelope. |
| get_download_urlA | Get a temporary download URL (valid 5 min) for signed documents from a completed envelope. |
| get_accountB | Get DigiSign account info — credits, plan, usage. |
| create_envelopeA | Create a new draft envelope for digital signature. Returns envelope ID for subsequent operations. |
| upload_and_attach_documentC | Upload a local file (PDF/DOCX) and attach it to an envelope. |
| add_recipientC | Add a signer, approver, or CC recipient to an envelope. |
| add_signature_tagB | Place a signature or form tag on a document. Use placeholder for text-based positioning or coordinates for exact placement. |
| send_envelopeB | Send a draft envelope for signature. Requires at least one document, one signer, and signature tags placed. |
| cancel_envelopeC | Cancel a sent envelope. Signers will be notified. |
| delete_envelopeA | Delete a draft envelope. Cannot delete sent/completed envelopes. |
| discard_envelopeA | Discard a draft envelope. Moves it to discarded state. Use this instead of delete when the API key lacks ROLE_ENVELOPE_DELETE. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.