> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# Authentication and Scopes for MCP Server

> Discover how to autheticate and the required scopes to use the Docusign MCP Server

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 Type  | Environment | URL |
| --------------- | ----------- | --- |
| Streamable HTTP | Demo        |     |
| Streamable HTTP | Production  |     |

## 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 Type                                                                                    | Advantages / Key Characteristics                                                                                              | Expiry & Token Refresh Behavior                                                                                                     | Best Suited For                                                                                           |
| ------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| [Confidential Authorization Code Grant](/platform/auth/authcode#confidential-authorization-code-grant) | **Supported 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) Grant](/platform/auth/jwt/jwt-get-token)                                         | Uses 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 Group             | Required Scopes                                          | Demo | Production |
| :-------------------- | :------------------------------------------------------- | :--: | :--------: |
| eSignature API        | `signature`                                              |   ✔  |      ✔     |
| CLM API               | `spring_read`, `spring_write`                            |   ✔  |      ✔     |
| Workflow Builder API  | `adm_store_unified_repo_read`, `aow_manage`, `signature` |   ✔  |      ✔     |
| Agreement Manager API | `adm_store_unified_repo_read`, `models_read`             |   ✔  |      ✔     |
| Connected Fields API  | `adm_store_unified_repo_read`, `signature`               |   ✔  |      ✖     |
| Data Verification API | `signature`                                              |   ✔  |      ✖     |
| Authentication tool   | `signature`                                              |   ✔  |      ✖     |
| Others                | `signature`                                              |   ✔  |      ✖     |

## Next steps

* Learn the various MCP tools available in the Docusign MCP server. See [MCP Tools](/platform/mcp-server/mcp-tools) to explore its capabilities.
* For more information on using production Docusign account with Docusign MCP server, see [Docusign MCP Server and AI Connector User Guide](https://support.docusign.com/s/document-item?language=en_US\&bundleId=ug3906200f-95c6-4a6b-90b1-f928c85961c6\&topicId=con1438e5dd-ae84-435f-8b2e-028117782a6d.html&_LANG=enus).