Docusign MCP server
Give your AI assistant 8 tools it can call in Docusign, over one server URL.
Docusign is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.
- Tools
- 8
- Works with
- Any MCP client
- Auth
- Custom auth
- License
- MIT, open source
- Updated
- September 2026
About the Docusign MCP server
Connect Docusign once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Docusign and 760+ other apps over a single connection, on our cloud or a self-hosted install.
Tools
Docusign tools your AI can run
Once connected, your assistant can call any of these Docusign actions by asking in plain language.
Search Signing Requests
Find and list signing requests with optional filters like status, date range, or keyword.
6 fields
Get Signing Request Details
Look up the full details of a signing request — status, recipients, and dates — using its ID.
2 fields
Download Document from Signing Request
Download a document (or all documents) from a signing request as a file.
3 fields
Send Document for Signing
Upload a document and send it to one or more people to sign via DocuSign.
7 fields
Update Signing Request
Send a draft, cancel, resend reminders, or edit the subject line on a signing request.
6 fields
Find Templates by Name
Search for reusable signing templates by name.
2 fields
Get People on a Signing Request
Get the full list of people on a signing request — signers, viewers, and anyone copied.
2 fields
Custom API Call
Make a custom API call to a specific endpoint
10 fields
Triggers
Docusign events your agent can watch
These start a run the moment something happens in Docusign, so work gets picked up on its own.
Signing Request Created
Triggers when a new signing request (envelope) is created in DocuSign — whether sent immediately or saved as a draft.
1 field
Signing Request Sent
Triggers when a signing request is emailed out to recipients for the first time.
1 field
Signing Request Opened by All
Triggers when every recipient has opened and viewed the signing request at least once.
1 field
Document Fully Signed
Triggers when everyone has completed their signature and the document is fully signed.
1 field
Signing Refused
Triggers when a recipient refuses to sign, stopping the signing process.
1 field
Signing Request Cancelled
Triggers when the sender cancels an in-progress signing request before everyone has signed.
1 field
Signing Email Sent to Person
Triggers when DocuSign sends the signing email to a specific person.
1 field
Person Opened Signing Request
Triggers when a specific person opens and views the signing request.
1 field
Person Signed Document
Triggers when a specific person completes their signature on the document.
1 field
Person Refused to Sign
Triggers when a specific person refuses to sign the document.
1 field
Person Failed Identity Check
Triggers when a recipient fails the identity verification step before signing.
1 field
Give your assistant Docusign
Connect Docusign once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.
Docusign MCP, answered.
No. That is the point of it. One Activepieces server exposes Docusign alongside every other piece you connect, so your client keeps a single connection.