Vendor: docusign.com · entry id 13-docusign · source 13-proposals-deals.md line 33
The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-08-24. On 2026-09-04 the recorded URL served a documentation page, not an MCP endpoint. That is where to read about the server, not where to connect to it. An agent needs the second.
mcp_status, verbatim from the file:
official (Open Beta)
mcp_url, verbatim from the file:
https://developers.docusign.com/platform/mcp-server/ ; hosted endpoint https://mcp.docusign.com/mcp ; announcement/community thread: https://community.docusign.com/general-74/building-with-ai-just-got-easier-introducing-the-docusign-mcp-server-25912
A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.
141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the tools index.
Install, as the source shows it:
npm install -g @docusign/agreement-cliquoted from https://www.npmjs.com/package/@docusign/agreement-cli on 2026-09-27, via npm
npm install -g @docusign-it/sfpdsquoted from https://www.npmjs.com/package/@docusign-it/sfpds on 2026-09-27, via npm
npm install -g @docusign/cliquoted from https://www.npmjs.com/package/@docusign/cli on 2026-09-27, via npm
Packages seen, with the version on 2026-09-27:
A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.
api_gate, verbatim from the file:
paid, tiered by envelope volume. DocuSign's Developer API plans run Starter ($50/mo or $600/yr, 40 envelopes/mo) through Intermediate ($300/mo, 100 envelopes/mo) to Advanced ($480/mo, unlocks Bulk Send/PowerForms/Connect webhooks) and Enterprise (custom); a free developer sandbox account exists for prototyping but is explicitly not production-usable. The MCP Server itself is described as available to both developer and production accounts in Open Beta with "no intake form or approval required," which is a notably low-friction access point relative to the metered envelope API underneath it.
No documentation URL recorded.
727 of 1252 entries are in the same position. Blank is legal and it is published as blank.
Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.
The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.
github.com/docusign tied to the vendor by rule 3, account website https://developers.docusign.com/ has the vendor's domain, confidence strong
The five most recently pushed, on 2026-09-08:
| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| PSA | other | Repo for all PSA assets | 1 | 2026-09-04 | workshop-kit-v1 |
| community-code-along | other | 1 | 2026-09-04 | ||
| code-examples-csharp | docs or examples | Docusign C# code examples and launcher | 64 | 2026-09-03 | v2018.12.18-1 |
| docusign-monitor-python-client | SDK | 2 | 2026-09-03 | v1.2.0 | |
| docusign-monitor-csharp-client | SDK | The Official DocuSign Charp Library used to interact with the Monitor REST API. | 0 | 2026-09-03 | v2.0.2 |
Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.
A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.
Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.
5 source URLs. Raw sources field, verbatim:
https://developers.docusign.com/platform/mcp-server/, https://mcpservers.org/remote-mcp-servers/docusign, https://www.pulsemcp.com/servers/docusign, https://www.docusign.com/blog/developers/claude-docusign-mcp-connector-guide, https://ecom.docusign.com/plans-and-pricing/developer
Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.