DocuSign MCP server

DocuSign × Claude Code

Use the DocuSign MCP server
in Claude Code

Send, track, and manage e-signature envelopes in DocuSign from your AI. This guide connects DocuSign to Claude Code (the terminal agent) 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 Code

Claude Code adds MCP servers via the `claude mcp add` command. The gateway route takes about two minutes:

  1. Connect DocuSign to your free gate gateway from the verified directory.
  2. In your terminal: claude mcp add gate https://gateturbo.com/api/mcp --transport http
  3. Approve the sign-in when Claude Code opens it in your browser.
  4. DocuSign's tools now appear in every Claude Code session — with per-tool allow/ask/block rules if you want them.

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, 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 Code 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 · DocuSign in ChatGPT · DocuSign in Cursor · DocuSign in VS Code