Docusign MCP Server
DocuSign eSignature API integration for envelope and template management via MCP.
Data last scanned today · Reviewed today
Overview
This Python-based MCP server facilitates interaction with the DocuSign eSignature API. It enables users to automate envelope workflows, manage document uploads, and leverage DocuSign templates directly through an AI assistant.
Our verdict
With a high-risk security score of 24/100, this server should be used with extreme caution. The project is community-maintained rather than official, and it lacks read-only mode, meaning every installation has full write access to your DocuSign account. Given the experimental status and reliance on sensitive JWT authentication, it is recommended for sandbox or testing environments only.
- Zero direct dependencies minimizes supply chain attack surface
- Comprehensive test coverage using pytest with mocks
- Uses JWT server-to-server authentication for headless operation
- High security risk due to full write access permissions
- Project status is experimental with no official maintenance
- Last code commit was over 275 days ago
Tools
| Tool | Description | Risk |
|---|---|---|
| create_envelope_from_template | Creates an envelope from a DocuSign template. | medium |
| create_envelope_from_documents | Creates an envelope from documents (not using a template). | medium |
| get_envelope_status | Gets status and metadata of an envelope. | low |
| list_envelopes | Lists envelopes with optional filters. | low |
| list_templates | Lists available DocuSign templates. | low |
| get_template_definition | Gets complete template definition. | low |
| list_envelope_documents | Lists all documents in an envelope. | low |
| download_envelope_document | Downloads a document from an envelope. | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What authentication method does this server use?
The server utilizes JWT OAuth for server-to-server authentication, which enables headless operation without requiring refresh tokens.
›What are the core technical requirements for running the server?
You need Python 3.11+, the uv package manager or pip, a DocuSign developer account, and an RSA keypair for JWT authentication.
›Is administrative consent required for this server to function?
Yes, a DocuSign account administrator must perform a one-time grant of consent for the 'signature' and 'impersonation' scopes.
›How should I handle my sensitive credentials like private keys?
Do not commit secrets to version control. Use a secrets manager to store your private keys and tokens.
›What should I check if I encounter 401 errors when accessing templates?
Verify that the assigned DocuSign user has 'Allow user to create and manage templates' enabled in their permissions settings and ensure your account supports the templates feature.
›Can I use this server in a production environment?
No, this project is currently marked as experimental, is not production-ready, and lacks a Service Level Agreement (SLA).
Badge
Maintain this server? Add the live badge to your README.