home / mcp / docusign mcp server
This read-only MCP Server allows you to connect to DocuSign data from Claude Desktop through CData JDBC Drivers. For full CRUD support, check out the first managed MCP platform: CData Connect AI (https://www.cdata.com/ai/).
Configuration
View docs{
"mcpServers": {
"cdatasoftware-docusign-mcp-server-by-cdata": {
"command": "java",
"args": [
"-jar",
"/PATH/TO/CDataMCP-jar-with-dependencies.jar",
"/PATH/TO/Salesforce.prp"
]
}
}
}This MCP Server for DocuSign lets you query live DocuSign data through a simple, local MCP interface. It exposes DocuSign data via the CData JDBC Driver as relational models, so you can ask questions in natural language and receive up-to-date answers without writing SQL. It is read-only for this deployment, making it safe for LLMs to fetch information from DocuSign data.
Connect with your MCP client to access the DocuSign data exposed by this server. You interact with the built-in tools by asking natural language questions about documents, envelopes, statuses, and related entities. You can request summaries, counts, statuses, and correlations across data such as which envelopes are in a given status, which accounts have most activity, or what dates certain events occurred.
Prerequisites you need before starting: - Java Runtime Environment (JRE) or JDK installed - Maven installed for building the server - A DocuSign account to access data via the CData JDBC Driver (or a trial/license of the driver)
git clone https://github.com/cdatasoftware/docusign-mcp-server-by-cdata.git
cd docusign-mcp-server-by-cdatamvn clean installDownload and install the CData JDBC Driver for DocuSign from the official site, then license it using the provided license utility in your environment.
java -jar cdata.jdbc.docusign.jar --licenseConfigure your DocuSign connection by running the JDBC driver’s connection utility, then save the resulting connection string for use in the server’s configuration.
java -jar cdata.jdbc.docusign.jarCreate a properties file for the JDBC connection (e.g., docusign.prp) and fill in the required fields including the JDBC URL you obtained from the previous step.
env
Prefix=docusign
ServerName=CDataDocusign
ServerVersion=1.0
DriverPath=PATH\\TO\\cdata.jdbc.docusign.jar
DriverClass=cdata.jdbc.docusign.DocusignDriver
JdbcUrl=jdbc:docusign:InitiateOAuth=GETANDREFRESH;
Tables=Create a Claude Desktop configuration to register the MCP server. Place the following in claude_desktop_config.json under the mcpServers section, or add it to your existing config if you already have one.
Windows JSON
{
"mcpServers": {
"docusign_mcp": {
"command": "PATH\\TO\\java.exe",
"args": [
"-jar",
"PATH\\TO\\CDataMCP-jar-with-dependencies.jar",
"PATH\\TO\\docusign.prp"
]
},
...
}
}Linux/Mac JSON
{
"mcpServers": {
"docusign_mcp": {
"command": "/PATH/TO/java",
"args": [
"-jar",
"/PATH/TO/CDataMCP-jar-with-dependencies.jar",
"/PATH/TO/docusign.prp"
]
},
...
}
}To run the MCP Server on its own, execute the following command. The server uses stdio and runs on the same machine as your client.
java -jar /PATH/TO/CDataMCP-jar-with-dependencies.jar /PATH/TO/Salesforce.prpIf you need to switch clients or refresh the MCP configuration, fully exit the client and start it again so the MCP server appears. You can ask the client questions like, “How many open envelopes are in my draft state?” or “Which users have the most activity this week?” The server provides read-only access to DocuSign data, making it suitable for exploratory data queries and live data insights.
Retrieves a list of tables available in the data source. The output is in CSV format with column headers.
Retrieves a list of columns for a specified table. The output is in CSV format with column headers.
Executes a SQL SELECT query against the data source and returns the results.