Labsco
MCP SERVER · OFFICIAL PROJECT

Docusign MCP Server

by Docusign ↗

Send agreements for signature, track their status and remind signers from an AI assistant.

Document Conversion, PDF & Translation✓ Popular vendor Official
Needed to connect
An account to sign in with
Tools
42 · from the project's docs
Setup effort
Follow the published steps
Source
Popular vendor Official

Most useful to the people who send agreements and chase signatures.

Teams send agreements, check where each one stands and remind pending signers without leaving their AI assistant; with an IAM subscription it also runs Workflow Builder workflows. Developers testing on a free developer (demo) account also get answers from Docusign's API documentation.

What it is

A remote MCP server Docusign runs for Claude, ChatGPT, Gemini, Copilot Studio, Perplexity, Slack and other AI assistants, with a production address and a demo address for developer accounts. It lets an AI assistant call Docusign's APIs in conversation; on a developer (demo) account it can also search Docusign's developer documentation.

What you get

  • Agreements generated and sent for signature from your templates, and envelope status checked
  • Your templates listed and filtered
  • Sent envelopes updated or voided, recipients changed, reminders sent to pending signers, and each recipient's status read
  • Workflow Builder workflows triggered, and agreements handled through Agreement Manager
  • Calls to Docusign's eSignature and CLM APIs; Connected Fields and Data Verification tools run on developer (demo) accounts only
  • On a developer (demo) account: answers from Docusign's developer documentation and integration best-practice advice
  • Your Docusign profile and account details

Requirements

  • For a live production account: a paid Docusign account, connected through Docusign's official connector (in Claude, the "Docusign" connector in the connectors directory).
  • For testing: a free Docusign developer account and a custom connector at the demo address https://mcp-d.docusign.com/mcp, using an Integration Key and secret you create under Apps and Keys as your own OAuth client.
  • Docusign advises against pointing a custom connector at the production address.
  • Claude needs a Pro plan or above for the custom connector.
  • Docusign publishes connector setup guides for Claude, ChatGPT, Gemini, Microsoft Copilot Studio, GitHub Copilot, Perplexity and Slackbot; the steps on this page are its Claude routes. Its Claude Code guide reuses a connector you first set up in Claude.
  • Workflow Builder and Agreement Manager actions need an IAM subscription; without one the call returns an upgrade notice.
  • Only on a developer (demo) account: documentation search, best-practice advice, access-token generation, Data Verification, Connected Fields, and brand and billing-plan lookups. To use them, connect a developer account at the demo address.

Setup effort

Follow the published steps