Build with the Docusign MCP Server | Docusign

The Docusign Model Context Protocol (MCP) server introduces a new way for developers to interact with Docusign APIs through natural, conversational AI interfaces. Instead of switching between documentation, API references, and code, you can now use any AI assistant that supports the MCP standard to explore Docusign’s capabilities, including generating access tokens, testing APIs, and automating end-to-end agreement workflows.

Prerequisites

If you are using a custom connector with a production Docusign account, ensure you

Submit this form with your integration key and email to allow-list your production Docusign account. For more details, refer here.

If you are using a custom connector with a developer Docusign account, you will need:

A Docusign developer account. You can create one.

The Docusign MCP server can connect to any AI-assisted tool powered by a large language model (LLM) platform. Here are a few examples of tools that support MCP:

Explore what’s possible with the Docusign MCP Server

The Docusign MCP Server makes it easier than ever to build and experiment with agreement workflows. You can ask natural language questions and receive clear, actionable answers about Docusign APIs and products directly from your preferred AI assistant or developer tool. It can also enable you to test or execute complex API operations with simple prompts, making tasks such as authentication, API testing, and envelope creation more efficient. Together, these capabilities work together to give you a more efficient, intelligent way to build with Docusign.

Use case	Example prompts
Learn about Docusign products	“Help me understand Workflow Builder and how I can use it in my application.” “My company builds healthcare software with an existing eSign integration. Can we use Docusign to provide agreement insights to our clients?” “I want to automate the full agreement workflow from creation to signature. What APIs do I use?”
Test APIs and automate workflows	“Show me how to implement Docusign APIs in my app and handle authentication securely.” “Generate a new agreement and send it for signature using my standard client onboarding template.” “Trigger the Workflow Builder workflow instance for my account.”

See the MCP server in action

Next steps

Learn the difference between official and custom MCP Server Connectors to explore its capabilities.
Learn how to authenticate and the list of scopes required to connect Docusign MCP server. See Authentication & Scope.
Learn the various MCP tools available in the Docusign MCP server. See 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.