DocuSign MCP Server (patched)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DS_USER_ID | Yes | User GUID to impersonate | |
| DS_AUTH_BASE | Yes | DocuSign authentication base URL: https://account-d.docusign.com (demo) or https://account.docusign.com (prod) | |
| DS_OAUTH_SCOPE | Yes | OAuth scope (e.g., signature impersonation) | signature impersonation |
| DS_PRIVATE_KEY | No | RSA private key, base64-encoded (single line) | |
| DS_INTEGRATION_KEY | Yes | DocuSign app Integration Key (client ID) | |
| DS_PRIVATE_KEY_PATH | No | Path to RSA private key file |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_envelope_from_templateA | Create an envelope from a DocuSign template. Args: template_id: The template ID to use. email_subject: Subject line for the email. role_assignments: List of role assignments with keys: - roleName: The role name in the template - name: Recipient's full name - email: Recipient's email address - clientUserId: (optional) For embedded signing email_blurb: Optional body text for the email. status: Envelope status - "sent" to send immediately or "created" for draft. Returns: Dictionary with envelopeId and status. |
| create_envelope_from_documentsA | Create an envelope from documents (not using a template). Args:
documents: List of documents, each with Returns: Dictionary with envelopeId and status. |
| get_envelope_statusA | Get the status and metadata of an envelope. Args: envelope_id: The envelope ID to query. Returns: Dictionary with envelope details including envelopeId, status, emailSubject, createdDateTime, sentDateTime, completedDateTime, etc. |
| list_envelopesA | List envelopes with optional filters. Args: from_date: Start date filter (ISO 8601 format, e.g., "2024-01-01T00:00:00Z"). to_date: End date filter (ISO 8601 format). status: Status filter (e.g., "sent", "delivered", "completed", "declined"). Returns: Dictionary with list of envelopes and metadata. |
| list_templatesA | List available DocuSign templates. Args: search_text: Optional search text to filter templates by name. Returns: Dictionary with list of templates and metadata. |
| get_template_definitionA | Get the definition and details of a specific template. Args: template_id: The template ID to retrieve. Returns: Dictionary with complete template details including roles, tabs, documents, and other metadata. |
| create_templateA | Create a new DocuSign template (documents + signer roles + signing fields). Args:
name: Template name.
documents: List of documents, each with Returns: Dictionary with templateId, name, uri. |
| list_envelope_documentsB | List all documents in an envelope. Args: envelope_id: The envelope ID to query. Returns: Dictionary with list of documents in the envelope. |
| download_envelope_documentA | Download a specific document from an envelope. Args: envelope_id: The envelope ID. document_id: The document ID to download. Returns: Dictionary with document content (base64-encoded) and metadata. |
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 9 tools
Each tool has a clear, distinct purpose: envelope creation (two distinct modes), envelope querying, document listing/downloading, and template operations are all well-separated. The only near-overlap is create_envelope_from_template vs create_envelope_from_documents, but their input parameters and use cases are clearly different.
All tool names follow a consistent verb_noun snake_case pattern (download_, get_, create_, list_). The two create_envelope variants are clearly named to indicate their source. No mixed conventions or vague verbs.
With 9 tools, the server is well-scoped for DocuSign envelope and template management. Each tool covers a meaningful operation without excessive fragmentation or redundancy.
The core lifecycle for envelopes (create, list, status, documents) and templates (create, list, get definition) is covered. Minor gaps exist: no envelope void/update, no template update/delete, but these are not critical for basic signing workflows and can be worked around.