Skip to main content

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 individual application pages.

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 relevant application page for what to collect)

Create an MCP server​

Find the API in the catalog​

  1. Sign in to AI Gateway and select MCP Servers from the left navigation.
  2. Select New MCP Server.
  3. Search for the application you want to connect, then select it from the catalog.

Configure the server​

  1. Enter a Name for your server — something descriptive that identifies both the application and its purpose (for example, "Zendesk Support — Prod").
  2. Enter a Description so your team knows what the server is for.
  3. Set the Timeout value. 30 seconds works for most APIs; increase to 60 seconds for APIs that return large payloads.
  4. Toggle Production mode on if this server will be used in a live workflow.
  5. Select Next.

Configure authentication​

Enter the authentication details for the application. This varies by service — see the Authentication section of the relevant application page for the specific credentials, OAuth URLs, and scopes to use.

Configure security​

  1. Set any Rate limits appropriate for your use case and the API's own limits.
  2. Enable Logging if you want AI Gateway to record requests and responses for auditing.
  3. Select Next.

Deploy​

Review the summary, then select 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.
  • You can edit a server's name, description, timeout, and security settings after deployment without redeploying.

Authentication​

DocuSign eSignature uses OAuth 2.0 JWT authentication. Create an integration key in DocuSign admin and generate an RSA key pair.

  • Authorization URL: https://account-d.docusign.com/oauth/auth
  • Token URL: https://account-d.docusign.com/oauth/token
  • Grant Type: urn:ietf:params:oauth:grant-type:jwt-bearer
  • Requires: Integration key, RSA private key, User ID, Account ID

Available tools​

The DocuSign eSignature MCP server exposes envelope management, template operations, signing workflows, recipient management, and document tracking APIs.

ToolPurpose
Envelope OperationsCreate and send envelopes; manage envelope status; void unsigned envelopes; retrieve envelope details
Document ManagementAdd documents to envelopes; manage document fields; configure signature placement; set document order
Recipient ConfigurationAdd signers and recipients; set signing order; configure recipient authentication; manage permissions
Signature FieldsPlace signature fields; add date fields; create initials fields; configure text and checkbox fields
TemplatesCreate reusable templates; manage template roles; configure default fields; clone templates
Embedded SigningGenerate recipient signing URLs; create sender view; customize signing experience
Workflow AutomationConfigure conditional routing; set up reminders; manage expiration; handle escalations
Compliance & AuditGet 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.