docusign-connector

Connect and operate DocuSign eSignature on the user's behalf via the official DocuSign eSignature REST API at `demo.docusign.net/restapi/v2.1` (sandbox) or `<base_uri>/restapi/v2.1` (production). Phase 1 is a 7-step Playwright-driven install: drive `admindemo.docusign.com/api-integrator-key` to create an Integration Key, DOM-extract the key, generate + capture a Secret Key from the one-time-reveal modal, register `http://localhost:8080/callback` as the Redirect URI, save, then drive DocuSign's OAuth Authorization Code Grant + PKCE flow with a local-listener exchange — the user signs in once, Claude auto-clicks Allow on the consent screen, the listener captures the code and exchanges it for an access token + 30-day refresh token in sub-second latency, and writes both into `~/.claude.json`. No DocuSign hosted MCP server is involved — DocuSign's `mcp.docusign.com` gateway rejects the OAuth-issued tokens (empirical finding 2026-05-05, issue #213). Phase 2 calls DocuSign's REST API directly via Bash + `curl`, with

By selrai-company schedule Updated 5/5/2026