docusign-mcp-server-by-cdata
A local, read-only MCP server that exposes DocuSign data via CData JDBC Driver (SQL-modeled tables/columns) to LLM clients (e.g., Claude Desktop) over MCP stdio. It provides MCP tools to list tables/columns and run SQL SELECT queries through the JDBC driver.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Communication is local stdio (no network endpoint), reducing external-in-transit exposure but increasing risk from local machine access. Auth details are delegated to the CData JDBC driver via connection string and (possibly) OAuth; the wrapper does not document fine-grained scopes. The server can execute SQL SELECT via run_query; a misbehaving agent could still exfiltrate more data than intended unless you restrict queries/permissions. README includes a local licensing step; it does not describe secret handling practices for the .prp/JdbcUrl contents.
⚡ Reliability
Best When
You want a local-only, same-host MCP integration where an LLM needs read-only access to DocuSign data modeled through CData JDBC, and you can supply the required JDBC driver + configuration (.prp).
Avoid When
You need internet-reachable access, strong API-level rate limiting, or comprehensive, machine-readable error/status guidance; or you cannot control the SQL the agent generates.
Use Cases
- • Query live DocuSign data from an LLM without writing SQL
- • Discover available DocuSign tables and columns via MCP tools
- • Run controlled read-only analytics queries (SELECT) against DocuSign-exposed relational models
Not For
- • Performing write/create/update/delete actions on DocuSign (described as read-only in this project)
- • Use as a network-accessible API for remote clients (stdio implies same-machine usage)
- • Handling unbounded/unsafe SQL generation without query constraints (the server supports run_query)
Interface
Authentication
The README indicates OAuth may be required depending on the underlying data source and that the JDBC driver connection string is configured in a local .prp file. Scope details are not described in this MCP wrapper.
Pricing
Pricing is not described for this repository. The JDBC driver licensing is required per the README; cost depends on CData driver/plan.
Agent Metadata
Known Gotchas
- ⚠ Server runs over stdio and 'can only be used with clients that run on the same machine as the server.'
- ⚠ The MCP tool surface includes a generic run_query method; agents may generate overly broad or expensive SQL unless constrained by your prompt/policy.
- ⚠ The .prp config requires correct DriverPath/DriverClass/JdbcUrl; misconfiguration is a common failure mode.
- ⚠ Claude Desktop may require fully quitting and reopening for MCP servers to appear.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for docusign-mcp-server-by-cdata.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.