DocuSign eSignature MCP server
DocuSign eSignature is the world's leading electronic signature solution enabling organizations to digitally prepare, sign, act on, and manage agreements. With this MCP server, AI agents can send documents for signing, manage envelopes, create templates, configure workflows, and track signature status through natural language commands.
Setting up an MCP server
This article covers the standard steps for creating an MCP server in AI Gateway and connecting it to an AI client. The steps are the same for every integration — application-specific details (API credentials, OAuth endpoints, and scopes) are covered in the Authentication section on this page.
Before you begin
You'll need:
- Access to AI Gateway with permission to create MCP servers.
- API credentials for the application you're connecting (see the Authentication section on this page for what to collect).
Create an MCP server
Find the app in the catalog
- Sign in to AI Gateway and select App Catalog from the left navigation.
- Search for the application you want to connect, then select it from the catalog.
- Select Create MCP Server to start the wizard.
App Configuration
Confirm the Base URL for the API, then, under Tools, select the endpoints you want to expose. Select Next.
MCP Server Setup
- Enter a Name for your server — something descriptive that identifies both the application and its purpose.
- Enter a Description so your team knows what the server is for.
- Set the log level: choose Production Mode for terser logs, or Non-Production Mode for more verbose logs that can help with debugging.
- Select Next.
Authentication
Enter the authentication details for the application. This varies by service — see the Authentication section on this page for the specific credentials, OAuth URLs, and scopes to use.
Review
Look over the summary of your MCP server configuration, then select Create & Deploy. AI Gateway provisions the server and provides a server URL you'll use when configuring your AI client.
Connect to an AI client
Once your server is deployed, you'll need to add it to the AI client your team uses. Select your client for setup instructions:
Tips
- You can create multiple MCP servers for the same application — for example, a read-only server for reporting agents and a read-write server for automation workflows.
- If you're unsure which OAuth scopes to request, start with the minimum read-only set and add write scopes only when needed. Most application pages include scope recommendations.
Authentication
DocuSign eSignature uses OAuth 2.0 JWT authentication. Create an integration key in DocuSign admin and generate an RSA key pair. In DocuSign Admin, go to Integrations > Apps and Keys and click Add App and Integration Key to create your integration key.
| Value | Setting |
|---|---|
| Auth endpoint | https://account-d.docusign.com/oauth/auth |
| Token endpoint | https://account-d.docusign.com/oauth/token |
| Grant type | urn:ietf:params:oauth:grant-type:jwt-bearer |
Available tools
The DocuSign eSignature MCP server exposes envelope management, template operations, signing workflows, recipient management, and document tracking APIs.
| Tool | Purpose |
|---|---|
| Envelope Operations | Create and send envelopes; manage envelope status; void unsigned envelopes; retrieve envelope details |
| Document Management | Add documents to envelopes; manage document fields; configure signature placement; set document order |
| Recipient Configuration | Add signers and recipients; set signing order; configure recipient authentication; manage permissions |
| Signature Fields | Place signature fields; add date fields; create initials fields; configure text and checkbox fields |
| Templates | Create reusable templates; manage template roles; configure default fields; clone templates |
| Embedded Signing | Generate recipient signing URLs; create sender view; customize signing experience |
| Workflow Automation | Configure conditional routing; set up reminders; manage expiration; handle escalations |
| Compliance & Audit | Get certificate of completion; track audit trails; export signed documents; monitor workflow status |
Tips
Create templates for repeated document types, define roles for flexible recipient assignment, set reasonable default field positions, and test templates thoroughly before production use.
Use anchor tags for automatic field placement, keep signing flow simple and intuitive, provide clear instructions in documents, and offer mobile-friendly signing.
Configure appropriate reminder schedules, set realistic expiration times, test escalation rules, and document conditional logic.
Use JWT authentication for server applications, implement webhook signature verification, encrypt sensitive data, and audit access logs.
Keep envelope history for audits, properly archive completed documents, maintain signature proof, and comply with retention policies.
Cequence AI Gateway