Connect your AI Agents to DocuSign in minutes

What is a DocuSign MCP server?

It’s an MCP server that lets you access data and functionality from a particular DocuSign instance via tools. Your agents can use these tools to download specific documents, fetch details on an envelope, list documents in an envelop, and more.

DocuSign offers an “official” MCP server, which is currently in Beta. You can also access DocuSign MCP servers from 3rd-party platforms, like Merge Agent Handler.

What are some popular DocuSign MCP server tools?

Here are some widely-used tools across resource types:

Documents

• <code class="blog_inline-code">list_documents</code>
• <code class="blog_inline-code">get_document</code>
• <code class="blog_inline-code">download_all_documents</code>
• <code class="blog_inline-code">add_document</code>

Envelopes

• <code class="blog_inline-code">get_envelop</code>
• <code class="blog_inline-code">create_envelop</code>
• <code class="blog_inline-code">send_envelop</code>
• <code class="blog_inline-code">resend_envelop</code>

Recipients

• <code class="blog_inline-code">update_recipients</code>
• <code class="blog_inline-code">list_recipients</code>
• <code class="blog_inline-code">delete_recipients</code>

What are some common ways to use a DocuSign MCP server?

Here are some popular use cases for your agents:

• Send documents for signature. Create an envelope, add recipients, and request specific fields like signatures and dates

• Create agreements from approved templates. Pick a standard template, fill in key details from your CRM or product data, and send it out for signature

• Run signing inside your product. Let users start and finish signing without leaving your app, while your agent handles the DocuSign steps in the background

• Monitor status and trigger next steps. Track when an envelope is viewed, signed, declined, or voided, then automatically kick off follow-up actions

• Store signed documents and audit trails. Download the completed agreement and its certificate, then save them to your system of record for compliance and easy retrieval

What makes Merge Agent Handler’s DocuSign MCP server better than alternative DocuSign MCP servers?

Here are a few reasons:

• Production-ready connector infrastructure: Merge Agent Handler provides a maintained, enterprise-grade integration layer on top of MCP that handles authentication, permissions, monitoring, and security for DocuSign tool calls
  

• Built-in authentication and credential management: Merge manages the full authentication lifecycle through registered users and Merge Link, which collects and stores connector credentials securely. This allows agents to access DocuSign tools without developers building custom OAuth flows, credential storage, or token refresh systems

• Configurable security controls with DLP: Merge routes tool inputs and outputs through a security gateway that can detect sensitive information and enforce policies. Teams can configure rules to warn, redact, or block risky DocuSign requests or responses before they reach the agent
  

• Real-time observability and auditability: Merge provides detailed monitoring for every tool interaction, including activity logs and a complete audit trail of DocuSign actions. The platform also exposes fully-searchable logs that show both the tool call and the underlying API request, making debugging and compliance review easier
  

• Testing and evaluation before production: Merge includes a Tool Pack Tester and an Evaluation Suite so teams can validate DocuSign tool behavior before deployment. The Evaluation Suite supports evaluator types like reference tool-call matching and label-based model evaluation to systematically test agent performance

Can I set custom security rules for DocuSign tool calls in Merge Agent Handler?

Yes, Merge Agent Handler’s security gateway scans both outbound requests from your agent to DocuSign and inbound responses from DocuSign back to your agent. 

Here are some custom rules you can set up:

• Prevent sending contracts to the wrong signer: Block DocuSign sends when the recipient domain is not on an allowlist, which helps avoid misrouted signature requests that expose pricing, terms, or customer data to unintended recipients

• Stop PII from being inserted into DocuSign fields: Block or redact tool calls when inputs include SSNs, passport numbers, or credit card patterns, which reduces the chance your agent accidentally shares regulated data in “message to signer” text or form fields

• Require approval before high-risk actions: Add a human approval step before an envelope is sent from an exec sender or for documents tagged as “MSA” or “DPA”, which gives Legal or Sales Ops a final review gate for irreversible actions

• Limit agreement value or discount exposure: Block sending when extracted terms exceed policy (like discount > 20% or total contract value above a threshold), which prevents unauthorized commercial terms from being issued by an automated workflow

• Prevent bulk or anomalous sending: Rate-limit or block if an agent tries to send unusually high volumes of envelopes in a short window, which reduces blast radius from prompt loops, misconfigurations, or compromised accounts

How can I start using Merge Agent Handler’s DocuSign MCP server?

You can follow these steps:

1. Create an Agent Handler account and sign in. 

2. Create a Tool Pack for DocuSign. In the dashboard, go to Tool Packs → Create new Tool Pack, then add the DocuSign connector to it (and only the tools you want exposed, if you’re scoping tightly).

3. Create a Registered User. In Registered Users, create a Registered User for the end user (or a service account) your agent will act on behalf of. Registered Users are the identity boundary that scopes credentials and logs.

4. Authenticate DocuSign for that Registered User. Have the end user connect their DocuSign account in the UI you embed (Merge Link). This is where third-party credentials get stored and scoped to that Registered User.

5. Copy the MCP connection details for “Tool Pack + Registered User”. You need the Tool Pack ID and Registered User ID to form the MCP URL your client will connect to.

6. Configure your MCP client with the Agent Handler MCP URL and your Agent Handler API key. Point your MCP client (Cursor, Claude Desktop, Windsurf, etc.) at the MCP URL that includes the Tool Pack ID and Registered User ID, and send your Agent Handler API key as a Bearer token in the Authorization header.

7. Test by listing tools and running a simple DocuSign action, then check Logs. Run a small prompt that triggers <code class="blog_inline-code">list_tools</code> and one <code class="blog_inline-code">call_tool</code>, then use the Logs page to verify what happened end-to-end.