Skip to Content

DocuSign MCP

Send documents for e-signature, track envelope and recipient status, void in-flight envelopes, and download completed agreements via the DocuSign eSignature REST API. High blast-radius — sends and voids legally-binding documents.

Overview

Catalog IDmcp-docusign
Categoryproductivity
Auth methodDocuSign OAuth access token (pasted)
Blast radiushigh
TrustVerified — published by cendriix
Version1.0.0
Regionsus-east-1, eu-west-1, ap-southeast-1

DocuSign is dispatched through a Cendriix-managed proxy onto the eSignature REST API v2.1 — there is no remote MCP server to connect to. DocuSign is not one of the providers registered for delegated consent, so the access token is supplied at install time rather than minted by an authorization flow.

Tools

ToolDescription
send_envelopeCreate and send an envelope for signature (or save it as a draft).
get_envelope_statusRead the current status and metadata of an envelope.
list_recipientsList an envelope’s recipients and their individual signing status.
void_envelopeVoid an in-flight envelope so it can no longer be signed.
download_completedDownload an envelope’s completed documents as one combined PDF.

Every tool takes accountId (your DocuSign account GUID) and an optional baseUri. DocuSign issues a per-account, per-region eSignature base URI — https://na1.docusign.net, https://eu.docusign.net, and so on — discovered from /oauth/userinfo when you connect. When baseUri is omitted it defaults to the demo host https://demo.docusign.net, so a misconfigured call fails loudly against the sandbox instead of quietly reaching the wrong production region.

Tool parameters

send_envelope

Create and send a DocuSign envelope for signature. Set status to created to save a draft instead of dispatching it.

ParameterTypeDescription
accountIdstringrequiredDocuSign account GUID
emailSubjectstringrequiredSubject line of the signing request email
documentsarrayoptionalDocuments to include: documentBase64, name, fileExtension, documentId
signersarrayoptionalSigner recipients: email, name, and optional recipientId / routingOrder
templateIdstringoptionalTemplate to base the envelope on, instead of inline documents
statusstringoptionalsent (default) dispatches immediately; created saves a draft
baseUristringoptionalAccount eSignature REST base URI

get_envelope_status

Retrieve the current status of an envelope — sent, delivered, completed, voided, and so on.

ParameterTypeDescription
accountIdstringrequiredDocuSign account GUID
envelopeIdstringrequiredThe envelope id to look up
baseUristringoptionalAccount eSignature REST base URI

list_recipients

List the recipients of an envelope and their individual signing status.

ParameterTypeDescription
accountIdstringrequiredDocuSign account GUID
envelopeIdstringrequiredThe envelope id whose recipients to list
baseUristringoptionalAccount eSignature REST base URI

void_envelope

Void an in-flight envelope. DocuSign requires a reason, which is recorded on the envelope’s history and visible to recipients.

ParameterTypeDescription
accountIdstringrequiredDocuSign account GUID
envelopeIdstringrequiredThe envelope id to void
voidedReasonstringrequiredWhy the envelope is being voided
baseUristringoptionalAccount eSignature REST base URI

download_completed

Download the completed, signed documents of an envelope as a single combined PDF, returned base64-encoded.

ParameterTypeDescription
accountIdstringrequiredDocuSign account GUID
envelopeIdstringrequiredThe envelope id whose documents to download
baseUristringoptionalAccount eSignature REST base URI

Installing

  1. In Cendriix, go to Settings → MCPs
  2. Find DocuSign and click Install
  3. Paste a DocuSign OAuth access token with the signature and extended scopes. It is validated, then encrypted at rest in a secrets vault scoped to your tenant.
  4. Note your account GUID and eSignature base URI from DocuSign’s /oauth/userinfo response — tools take them as arguments, because a single DocuSign login can hold several accounts in different regions.
  5. Click Test Connection to run a health check and list available tools

Authentication. DocuSign access tokens are short-lived. Because DocuSign is not registered for delegated consent, Cendriix cannot refresh this token for you: when it expires, tool calls return 401 and the token must be replaced. If you want unattended DocuSign automation, tell us — registering DocuSign as an OAuth provider is catalog configuration on our side, not a rebuild.

Blast radius

This MCP is classified high, and the classification is literal: send_envelope puts a legally-binding agreement in front of a signer and void_envelope withdraws one. Gate both in Policies before letting an agent use this MCP unattended.

Every tool invocation is recorded in your Audit Log. You can remove this MCP at any time from Settings → MCPs, which revokes tool access immediately.

Maturity

The DocuSign proxy is built to the same pattern as our other managed proxies but has not yet been exercised against a live DocuSign account. Treat it as preview: validate a send → status → download round-trip in a DocuSign demo account before pointing it at production agreements, and note that download_completed returns base64 across a text transport, so binary fidelity is worth confirming on a real completed envelope.

Further reading

Last updated on