Docusign Connector
Gives Claude read & write access to DocuSign agreements — generate contracts from templates, route for review, search/surface agreements (e.g. "contracts expiring in 90 days"), and trigger workflow automations.
https://claude.com/connectors/docusign
By DocuSign, Inc.
How to Get It
Trust Signals Auto-scanned
Not yet scanned. Learn how to check this tool yourself.
Data & Access
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
claude.com/connectors/docusign discloses no authentication method and doesn't explicitly state GA/beta on the page itself, but the vendor's own MCP server documentation page (developers.docusign.com/platform/mcp-server/) is explicitly titled/labeled 'Beta' — capping this per the stated beta-caps-security-at-4 rule, and pulling client_readiness down for the same reason (a consultant should flag beta status before recommending this for client contract workflows). The functional scope is broad and genuinely valuable (contract creation, review-and-suggest against company policy, expiring-agreement search) across sales, legal, procurement, and HR. DocuSign the company is a major, long-established public company (NASDAQ: DOCU) and category leader in e-signature, which supports a solid reliability score even though this specific MCP integration is new. | Sentiment: No direct community sentiment found on DocuSign's own connector; HN search turned up only unrelated third-party e-signature MCP projects, not reviews of this integration. | Ensemble: median of 86 independent doc+sentiment evaluations (official-coverage sweep 2026-07-23).
Things to check
- The underlying MCP server is explicitly Beta per DocuSign's own docs — this should be disclosed to any client before deployment given it grants read & write access to legal agreements (financial terms, signatures, PII). No auth mechanism is documented on either the Anthropic connector page or the vendor page I could reach. No independent sentiment found this session (WebSearch quota exhausted, firecrawl out of credits); HN search surfaced only unrelated third-party e-signature/MCP projects (Signbee, SafeApeals, SaySigned), not reaction to DocuSign's own connector.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
claude.com/connectors/docusign discloses no authentication method and doesn't explicitly state GA/beta on the page itself, but the vendor's own MCP server documentation page (developers.docusign.com/platform/mcp-server/) is explicitly titled/labeled 'Beta' — capping this per the stated beta-caps-security-at-4 rule, and pulling client_readiness down for the same reason (a consultant should flag beta status before recommending this for client contract workflows). The functional scope is broad and genuinely valuable (contract creation, review-and-suggest against company policy, expiring-agreement search) across sales, legal, procurement, and HR. DocuSign the company is a major, long-established public company (NASDAQ: DOCU) and category leader in e-signature, which supports a solid reliability score even though this specific MCP integration is new. | Sentiment: No direct community sentiment found on DocuSign's own connector; HN search turned up only unrelated third-party e-signature MCP projects, not reviews of this integration. | Ensemble: median of 86 independent doc+sentiment evaluations (official-coverage sweep 2026-07-23).