DocuSign MCP server

DocuSign × Claude

Use the DocuSign MCP server
in Claude

Send, track, and manage e-signature envelopes in DocuSign from your AI. This guide connects DocuSign to Claude (claude.ai and the Claude desktop app) through a governed gateway — one URL that also works in every other MCP client you use, with your rules and a full log attached.

Live-probed · Security-scanned · Note: DocuSign currently restricts third-party sign-ins — API-key path recommended

Setup: DocuSign in Claude

Claude adds MCP servers via custom connectors in Settings. The gateway route takes about two minutes:

  1. Create a free gate gateway and connect DocuSign to it from the verified directory (one click — note: DocuSign currently restricts third-party sign-ins, so use the API-key path if the vendor offers one).
  2. Open claude.ai → Settings → Connectors and click 'Add custom connector'.
  3. Name it 'gate' and paste your gateway URL, then approve the authorization.
  4. Ask Claude something DocuSign can answer — the call runs through your gateway, with your rules applied and logged.

What to ask once it’s connected

Which envelopes are still waiting for a signature?
Send the NDA template to this new partner.
What's the status of the Q3 contract?
Remind everyone who hasn't signed yet.

Why route it through a gateway

One URL, every client

The same DocuSign connection works in Claude Code, ChatGPT, Cursor, VS Code too — no per-client re-wiring.

Rules before regret

Allow, ask, or block every tool DocuSign exposes — reads can flow freely while writes require your approval.

Every call logged

A plain-language activity log of everything Claude did with DocuSign — searchable, exportable, auditable.

Scanned and probed

DocuSign passed a live handshake probe and a security scan before listing — and drift detection watches it after you connect.

Also available: DocuSign in Claude Code · DocuSign in ChatGPT · DocuSign in Cursor · DocuSign in VS Code