t1k:business:docusign-esign
| Field | Value |
|---|---|
| Module | base |
| Version | 0.12.1 |
| Effort | low |
| Tools | — |
Keywords: docusign, docusign demo, docusign envelope, docusign integration key, docusign mcp, docusign setup, envelope, envelope status, integration key, mcp.docusign.com, send envelope, void envelope
How to invoke
Section titled “How to invoke”/t1k:business:docusign-esignsetup [--demo] | status | envelope <id> | list | send <id> | void <id>DocuSign E-Signature (MCP)
Section titled “DocuSign E-Signature (MCP)”Drive DocuSign envelopes from Claude Code through DocuSign’s official MCP server. This is the DocuSign counterpart of t1k:business:pandadoc-esign: PandaDoc remains the studio default for documents we originate; use this skill when a counterparty or deal requires DocuSign, or to read an existing DocuSign envelope (e.g. a counterparty-initiated Abysscore-style envelope).
The server is optional: it is declared in t1k-config-business.json under mcp.optional (surfaced by the core MCP health check until registered, then silent).
Facts (verified 2026-10-02)
Section titled “Facts (verified 2026-10-02)”| Production | Demo / developer | |
|---|---|---|
| Endpoint (Streamable HTTP) | https://mcp.docusign.com/mcp | https://mcp-d.docusign.com/mcp |
| Registered name | docusign | docusign-demo |
- Auth is OAuth 2.0 Authorization Code + PKCE (S256) against
https://account.docusign.com. Scopes:signature,adm_store_unified_repo_read,aow_manage,spring_read,spring_write,cors. - The authorization server has no
registration_endpoint(no dynamic client registration). Claude Code cannot self-register, so every user needs a pre-registered Integration Key. - Docs: https://developers.docusign.com/platform/mcp-server/ and https://www.docusign.com/blog/developers/claude-docusign-mcp-connector-guide
Setup (one-time, per person, own key)
Section titled “Setup (one-time, per person, own key)”-
Create your own Integration Key: DocuSign Admin > Apps and Keys > Add App and Integration Key > Authorization Code Grant. Prefer the public/PKCE “no secret” client if offered. Set the Redirect URI to exactly
http://localhost:9104/callback. Port 9104 is the studio-allocated callback port (8765 is taken on dev machines). -
Register the server with the helper (key is a public GUID, safe as an arg):
Terminal window ~/.claude/skills/t1k-business-docusign-esign/scripts/install-docusign-mcp.sh <INTEGRATION_KEY> # production~/.claude/skills/t1k-business-docusign-esign/scripts/install-docusign-mcp.sh <INTEGRATION_KEY> --demo # demo accountIt validates the GUID, replaces any existing entry, and runs
claude mcp add --transport http … -s user --client-id <KEY> --callback-port 9104. If your app has a secret, add--with-secret(Claude prompts) or exportMCP_CLIENT_SECRET. Never put the secret in argv, a chat message, or a file; the script refuses--client-secret=…. -
Restart Claude Code, run
/mcp, selectdocusign, Authenticate (browser login). Tools then appear asmcp__docusign__*(deferred:ToolSearch(query="docusign")first; bind to whatever names the server exposes).
Alternative for production accounts: the prebuilt claude.ai connector (Settings > Connectors > DocuSign). It ties DocuSign to the Claude login account, so the studio standard is the own-key route above.
Operations
Section titled “Operations”Read first, write second, outward-facing last.
| Tier | Operations | Policy |
|---|---|---|
| Read | list/inspect envelopes, status, recipients, audit events, download executed docs | safe |
| Draft | create an envelope as a draft, add documents/recipients/tabs | show the user what you create |
| Outward (gated) | send, void, resend/correct a sent envelope | HARD GATE below |
⛔ HARD GATE — NEVER send or void an envelope without the user’s explicit, per-action approval. Sending transmits the document to the counterparty for signature; voiding cancels an in-flight signature. Both are outward-facing and hard to reverse. Before either, show the user the envelope title/id and the full recipient list and get an explicit “yes, send” (or “yes, void”) for that specific envelope, every time. No standing approval, no inferring intent from earlier turns. When unsure, leave the envelope in draft. This mirrors the PandaDoc send-gate policy; unlike PandaDoc there is currently no PreToolUse hook enforcing it for
mcp__docusign__*, so the discipline is yours. Never route around the gate.
Follow the consuming project’s e-sign conventions (required CC recipients, routing order, render-equivalence with the full contract) as defined in its AGENTS.md/CLAUDE.md; the same rules that apply to PandaDoc sends apply here. Whatever the project says, the signing render must stay legally equivalent to the full contract .docx (never drop a liability cap or IP carve-out). Render contracts first with t1k:business:contract; contracts we originate default to t1k:business:pandadoc-esign.
Executed by
Section titled “Executed by”Setup runs in t1k-mcp-manager (or inline): scripts/install-docusign-mcp.sh is deterministic (validate key, claude mcp add). Creating, sending and voiding envelopes, and every approval decision, stay reasoning-tier in the main session.
| Step | Agent |
|---|---|
Register the MCP server via install-docusign-mcp.sh | t1k-mcp-manager |
| Envelope operations and the send/void gate | main session |
Related
Section titled “Related”t1k:business:pandadoc-esign (default e-sign path, send-gate hook) - t1k:business:contract (render) - t1k:business:contract-review (review before sending).