Skip to navigation
Platform 101MCP Server

Comparing Official and Custom Connector

View as Markdown

Before you connect Docusign account to your preferred AI assistant, it’s important to understand the two ways to set up the integration:

  • Official connector
  • Custom connector

Each serves a different purpose, and choosing the right one from the start saves you time and avoids misconfiguration.

Official ConnectorCustom Connector
PurposeProduction useTesting and exploration
Docusign AccountProduction accountDemo account (recommended)
SetupGuided, pre-built integrationManual configuration
Recommended forBusiness and enterprise usersFirst-time users, developers
SupportOfficially supportedCommunity / self-managed

Official connectors are the verified, supported integration built for connecting your Production Docusign account to your AI assistant. They are maintained and published by Docusign and follow the security and compliance standards expected for production workloads.

Custom connectors walkthrough in this documentation is designed specifically for you to explore the Docusign MCP server using a Developer Docusign account. It lets you explore the various range of MCP tools available like sending envelopes, checking status, managing templates, etc.Custom connectors connected directly to the MCP server URL may give you earlier access to newly released tools during the preview phase.

Choosing the Right Connector for Production Accounts

Important:

  • If an official connector exists (e.g., in Claude, ChatGPT):
    ➜ Use the official connector. Configuring a custom connector for production is not recommended.
  • If no official connector exists for your AI platform or LLM:
    ➜ Use a custom connector. You may route it to the Docusign production MCP URL.

For setup instructions, refer to the Custom Connector Setup Guide.

If you are already using your production MCP Docusign URL in a custom connector, follow this process to go-live with production account.

Use this decision flowchart before you begin setup:

I want to…Use this
Try Docusign MCP tools for the first timeCustom Connector
Test in a sandbox before going liveCustom Connector
Connect a live production accountOfficial Connector
Use this in a business/enterprise contextOfficial Connector

Both custom and official connectors are available across the following platforms. Use the links below to navigate to the right setup guide for your AI assistant.

AI AssistantOfficial ConnectorCustom Connector
Anthropic ClaudeAnthropic ClaudeAnthropic (Claude)
GitHub CopilotNot AvailableGitHub (Copilot)
Google Gemini EnterpriseGoogle Gemini EnterpriseNot Available
Microsoft Copilot StudioMicrosoft Copilot StudioMicrosoft Copilot Studio
OpenAI ChatGPTOpenAI ChatGPTOpenAI ChatGPT
PerplexityPerplexityPerplexity
SlackbotSlack (Slackbot)Slack (Slackbot)

  • Authentication scope differences: Custom connectors may require you to manually provide and rotate API keys or OAuth tokens. Official connectors often handle token refresh and scope management automatically, reducing the risk of authentication failures in long-running workflows.

  • Rate limiting behavior: Demo accounts and production accounts have different API rate limits in Docusign. Using a custom connector pointed at a production URL from a development setup could unexpectedly consume your production API quota during testing.

  • Auditability: Actions taken through official connectors may be logged differently within Docusign’s audit trail compared to custom connector calls, which could matter for compliance-sensitive organizations.

  • Feature parity lag: Official connectors may not expose every MCP tool immediately when new tools are added to the DocuSign MCP server. Custom connectors connected directly to the MCP server URL may give you earlier access to newly released tools during the preview phase.

  • Multiple production accounts: If you manage multiple production Docusign accounts for different teams or business units, the custom connector gives you flexibility to test different accounts, whereas official connectors are typically tied to their individual Docusign account.

    • If an individual is part of multiple accounts in Docusign, they can access all their accounts in official connector. They can choose to disable the MCP access under their individual accounts in the admin screen.

Next steps