Docusign
Docusign's official MCP server gives AI agents access to agreements, envelopes and eSignature workflows through your Docusign account.
Docusign does not support dynamic client registration, so you create an app in Docusign first and paste its credentials into Willow. Willow already knows Docusign's OAuth endpoints and scopes, so the only values you need to copy are the Integration Key and the Secret Key.
Prerequisites
- A Docusign account with administrator access
- Permission to create apps under Apps and Keys
Choose an environment
| Environment | MCP endpoint | Use it for |
|---|---|---|
| Production | https://mcp.docusign.com/mcp | Production Docusign accounts |
| Demo | https://mcp-d.docusign.com/mcp | Developer accounts |
Pick the environment in Willow when you add the server; Willow points OAuth at the matching Docusign authorization server automatically.
Steps
1. In Willow — start adding the server
- Go to Add MCP Server and search for Docusign in the registry
- Click + Use on the official Docusign card
- Select the Environment that matches your Docusign account
Keep this dialog open — it shows the setup steps and the redirect URL you need in the next step.
2. In Docusign — create the app
- Sign in to Docusign as an administrator
- Go to Settings -> Integrations -> Apps and Keys
- Click Add App and Integration Key
- Name the app
Willowand click Create App - Set the integration type to Private custom integration (Authorization Code Grant)
- Click + Add Secret Key and copy the generated secret — Docusign shows it only once
- Under Redirect URIs, click Add URI and paste the redirect URL from Willow:
- SaaS deployments:
https://{org}.mcp-s.com/{org}/api/auth/callback - On-premise deployments:
{connectUrl}/{org}/api/auth/callback
- SaaS deployments:
- Under Allowed HTTP Methods, select all methods
- Click Save
3. Back in Willow — paste the credentials
- Copy the Integration Key from the Docusign app page and paste it as the Client ID
- Paste the Secret Key as the Client Secret
- Create the integration
Willow requests the signature, adm_store_unified_repo_read and aow_manage scopes. Users are prompted to authorize Docusign the first time they call a Docusign tool.
You can revisit these steps at any time from the integration's Setup tab using the Setup wizard and Docs buttons.
Troubleshooting
Redirect URI mismatch
Docusign rejects the authorization request when the redirect URI does not match exactly. Copy the URL straight from Willow rather than typing it, and make sure you added it to the app in the same environment (demo apps and production apps have separate redirect URI lists).
Consent required for your organization
If your Docusign organization requires admin consent, an administrator must grant consent for the app before other users can authorize it. See Docusign's MCP server documentation for details.