Skip to main content

Configure DocuSign for the AI Gateway

To allow your users to securely send envelopes, manage signing workflows, and generate signing links using their AI clients, you can configure the DocuSign Model Context Protocol (MCP) server within the JumpCloud AI Gateway.

Prerequisites​

  • Before configuring specific enterprise applications, we recommend reviewing the Get Started: AI Gateway guide to familiarize yourself with the gateway architecture and core AI concepts (such as MCP servers and AI clients).

  • Access to a DocuSign developer (sandbox) or production account where you can create an integration app and manage OAuth credentials.

  • For production, a DocuSign integration key approved for MCP access. See DocuSign’s production approval requirements.

Completing Application Setup​

Create a DocuSign integration app to obtain the OAuth credentials you’ll enter in JumpCloud. See DocuSign’s Build with the Docusign MCP Server for setup requirements.

Important

DocuSign recommends its official connectors for production accounts and requires approval for production integration keys used with custom connectors. Review its MCP server guidance before configuring production access.

In the DocuSign account for the environment you want to connect, configure the following:

  • Integration app: Go to Settings > Integrations > Apps and Keys and click Add App and Integration Key. Copy the Integration Key to use as the Client ID in JumpCloud.
  • Client secret: Under Authentication, click Add Secret Key. Copy the value when it appears; DocuSign shows it only once.
  • Redirect URIs: Under Additional settings > Redirect URIs, add the JumpCloud AI Gateway Redirect URL for your region:
    • US: https://console.jumpcloud.com/userconsole/mcp/servers/callback
    • EU: https://console.eu.jumpcloud.com/userconsole/mcp/servers/callback
    • IN: https://console.in.jumpcloud.com/userconsole/mcp/servers/callback

If you’re moving a sandbox integration to production, complete DocuSign’s Go-Live process and configure the production Secret Key and Redirect URIs.

note

The registered redirect URI must match the JumpCloud callback URL exactly. A mismatch causes an invalid_redirect_uri error.

Configuring the Server in JumpCloud​

See Adding MCP Servers in Configure AI Gateway Integrations and use the following values to configure this server:

  • App: Select DocuSign (if you have an existing SSO application or bookmark), or + Add App to create it
  • Name: Enter a name, for example DocuSign
  • Prefix: Enter a value to prepend to MCP tool names
    • Note: Prefixes must be unique. Maximum 8 characters, letters and numbers only
  • URL: Enter the DocuSign MCP server URL for your environment:
    • Production: https://mcp.docusign.com/mcp
    • Sandbox (developer): https://mcp-d.docusign.com/mcp
  • MCP Authentication method: Select OAuth
  • Advanced fields: Enter the following:
    • Client ID: Your DocuSign Integration Key
    • Client Secret: Your DocuSign Secret Key
    • Scope: signature extended. The signature scope permits eSignature API access. The extended scope gives each renewed refresh token a new validity period. See DocuSign’s Authentication scopes to learn more.

Your users will now see DocuSign listed as an available application when they authenticate their AI clients through the JumpCloud AI Gateway.

Was this information helpful?