Build DocuSign-Powered Applications in GitHub Copilot with CData Code Assist MCP

GitHub Copilot is an AI-powered coding assistant that integrates directly into Visual Studio Code and other IDEs. With support for MCP, GitHub Copilot can connect to local tools and enterprise data sources, enabling natural language interaction with live systems during development.

Model Context Protocol (MCP) is an open standard for connecting LLM clients to external services through structured tool interfaces. MCP servers expose capabilities such as schema discovery and live querying, allowing AI agents to retrieve and reason over real-time data safely and consistently.

In this article, we guide you through installing the CData Code Assist MCP for DocuSign, configuring the connection to DocuSign, connecting the Code Assist MCP add-on to GitHub Copilot, and querying live DocuSign data from within Visual Studio Code.

Prerequisites

• Visual Studio Code is installed on your machine
• GitHub Copilot Chat extension is enabled in Visual Studio Code
• CData Code Assist MCP for DocuSign has been installed

Step 1: Download and install the CData Code Assist MCP for DocuSign

1. To begin, download the CData Code Assist MCP for DocuSign 👁 Downloading the CData Code Assist MCP add-on installer
   
2. Find and double-click the installer to begin the installation
3. Run the installer and follow the prompts to complete the installation 👁 Completing the CData Code Assist MCP add-on installation
   

When the installation is complete, you are ready to configure your Code Assist MCP add-on by connecting to DocuSign.

Step 2: Configure the connection to DocuSign

1. After installation, open the CData Code Assist MCP for DocuSign configuration wizard 👁 The CData Code Assist MCP add-on configuration wizard
   

   NOTE: If the wizard does not open automatically, search for "CData Code Assist MCP for DocuSign" in the Windows search bar and open the application.

   👁 Opening the CData Code Assist MCP add-on configuration wizard (Google Sheets is shown).
   
2. In MCP Configuration > Configuration Name, either select an existing configuration or choose to create a new one 👁 Creating a new configuration
   
3. Name the configuration (e.g. "cdata_docusign") and click OK 👁 Naming the configuration
   

4. Enter the appropriate connection properties in the configuration wizard

   To connect to DocuSign, set the following connection properties:

   • UseSandbox: indicates whether current user account is sandbox or not (FALSE by default)
   • AccountId (optional): set it in the connection string if you have access to multiple Account Ids

   Authenticating to DocuSign

   DocuSign uses the OAuth authentication standard. To authenticate using OAuth, create an app to obtain the OAuthClientId, OAuthClientSecret, and CallbackURL connection properties. See the Help documentation more information. 👁 Configuring the Code Assist MCP add-on connection
   

5. Click Connect to authenticate with DocuSign through OAuth
6. Click Save & Test to finalize the connection 👁 Saving and testing the Code Assist MCP add-on configuration
   

This process creates a .mcp configuration file that GitHub Copilot will reference when launching the Code Assist MCP add-on. Now with your Code Assist MCP add-on configured, you are ready to connect it to GitHub Copilot.

Step 3: Connect the Code Assist MCP add-on to GitHub Copilot

1. Download and install Visual Studio Code and enable the GitHub Copilot Chat extension

Option 1: Manually add the MCP configuration

1. Open or create the mcp.json file:
   • For global configuration: %%APPDATA%%/Roaming/Code/User/mcp.json
   • For project-specific configuration:
2. Add the JSON code shown below and save the file

{
 "servers": {
 "cdata_docusign": {
 "command": "C:\Program Files\CData\CData Code Assist MCP for DocuSign\jre\bin\java.exe",
 "args": [
 "-Dfile.encoding=UTF-8",
 "-jar",
 "C:\Program Files\CData\CData Code Assist MCP for DocuSign\lib\cdata.mcp.docusign.jar",
 "cdata_docusign"
 ]
 }
 }
}

NOTE: The command value should point to your Java 17+ java.exe executable, and the JAR path should point to the installed CData Code Assist MCP add-on .jar file. The final argument must match the MCP configuration name you saved in the CData configuration wizard (e.g. "cdata_docusign").

Option 2: Copy the MCP configuration from the CData Code Assist MCP for DocuSign UI

1. After saving and testing your connection in the configuration wizard, click Next 👁 Selecting 'Next'
   
2. Select Github Copilot from the AI MCP Tool dropdown 👁 Choosing GitHub Copilot as the AI MCP tool
   
3. Follow the MCP Client Instructions to create the required configuration file 👁 MCP configuration instructions for GitHub Copilot
   
4. Copy the displayed JSON code and paste it into your configuration file

Step 4: Query live DocuSign data in GitHub Copilot

1. Launch Visual Studio Code and open the GitHub Copilot Chat interface. Select the tool icon to enable the configured Code Assist MCP add-on 👁 Enabling the CData Code Assist MCP add-on in GitHub Copilot
   
2. Ask questions about your DocuSign data using natural language. For example:

   "List all tables available in my DocuSign data data connection."

   👁 Querying live data from GitHub Copilot
   
3. Start building with natural language prompts:

   For my project, data from the Documents is very important. Pull data from the most important columns like DocumentId and DocumentName.
   

GitHub Copilot is now fully integrated with CData Code Assist MCP for DocuSign and can use the MCP tools to explore schemas and execute live queries against DocuSign.

Build with Code Assist MCP. Deploy with CData Drivers.

Download Code Assist MCP for free and give your AI tools schema-aware access to live DocuSign data during development. When you're ready to move to production, CData DocuSign Drivers deliver the same SQL-based access with enterprise-grade performance, security, and reliability.

Visit the CData Community to share insights, ask questions, and explore what's possible with MCP-powered AI workflows.