Skip to navigation
Platform 101MCP Server

Authentication and Scopes for MCP Server

View as Markdown

You can connect to the Docusign MCP server through a variety of compatible AI assistants and developer tools. This guide demonstrates how to configure and interact with the Docusign MCP server.

Use the following Docusign MCP URLs for the demo and production environments.

Transport TypeEnvironmentURL
Streamable HTTPDemohttps://mcp-d.docusign.com/mcp
Streamable HTTPProductionhttps://mcp.docusign.com/mcp

Authentication

To interact with the MCP server, you’ll need a valid OAuth access token. Docusign MCP server supports access tokens for Confidential Authorization Code Grant and JWT Grant OAuth grant type.

The below table mentions the authentication types, its advantages and limitations.

Authentication TypeAdvantages / Key CharacteristicsExpiry & Token Refresh BehaviorBest Suited For
Confidential Authorization Code GrantSupported by Docusign MCP Server
Keeps LLMs connected seamlessly without manual intervention.		Automatic Refresh
No manual token renewal required; maintains continuous connection for LLMs.		Integrations with the Docusign MCP Server requiring long-running, uninterrupted AI model connections.
JSON Web Token (JWT) GrantUses a single system/service account to make calls on behalf of users.
Ideal for automated system-to-system background tasks.		Expires in one hour after generation.
Client applications are responsible for requesting a new token before or upon expiration.		Automated background service integrations and server-to-server workflows.

Scopes

API GroupRequired ScopesDemoProduction
eSignature APIsignature✔✔
CLM APIspring_read, spring_write✔✔
Workflow Builder APIadm_store_unified_repo_read, aow_manage, signature✔✔
Agreement Manager APIadm_store_unified_repo_read, models_read✔✔
Connected Fields APIadm_store_unified_repo_read, signature✔✖
Data Verification APIsignature✔✖
Authentication toolsignature✔✖
Otherssignature✔✖

Next steps