swiftsign-mcp

E-signature for AI agents. An MCP server that lets Claude Code, Cursor, Zed, or any MCP-aware agent prepare, send, track, and seal legally binding documents without a human ever touching a mouse.

DocuSign assumes a person with a cursor dragging signature boxes onto a PDF. SwiftSign assumes code. An agent mints its own sandbox key, sends a contract, watches it get signed, and pulls back the sealed PDF and Certificate of Completion. No drag handles. No per-seat fees.

Quick start

claude mcp add swiftsign -- npx -y swiftsign-mcp

Or add it to your .mcp.json directly:

{
  "mcpServers": {
    "swiftsign": {
      "command": "npx",
      "args": ["-y", "swiftsign-mcp"],
      "env": { "SWIFTSIGN_API_KEY": "sk_test_..." }
    }
  }
}

No key yet? You do not need the dashboard. Start the server with no key and call swiftsign_signup to mint a sandbox key in one tool call.

Related MCP server: SignForge

Zero to signed, no browser

An agent can go from nothing to a sealed document without ever opening a web page:

1.  swiftsign_signup          → mint a sandbox key (sk_test_...), no account, no card
2.  swiftsign_send_envelope   → send a PDF, place fields by anchor text or coordinates
3.  swiftsign_check_status    → poll until signed
4.  swiftsign_download_signed_pdf → pull back the sealed PDF + Certificate of Completion

Live sends are confirm-gated: a real, legally binding send requires an explicit swiftsign_confirm_send so an agent cannot fire a contract by accident.

Tools

Coming from DocuSign

Bring your existing templates with you. The bundled importer (src/docusign/) authenticates against the DocuSign API and maps your templates and fields into SwiftSign, so an agent can migrate a signing workflow instead of rebuilding it.

Sandbox vs live keys

• sk_test_: everything works (send, status, templates, embedded URLs); documents are test sends. No card.

• sk_live_: real, legally binding documents. Upgrade once with swiftsign_upgrade (a Stripe link you open to add a card). The same tools work in both modes; the key decides.

Legally binding

SwiftSign signatures carry a tamper-evident SHA-256 seal, a full audit trail, and a Certificate of Completion. Enforceable under:

• United States: ESIGN Act, UETA

• Canada: PIPEDA, Ontario Electronic Commerce Act

Configuration

Build from source

npm install
npm run build      # compiles src/ → dist/
npm test           # node --test

Links

• Website: swiftsign.ca

• API docs: swiftsign.ca/docs

• Issues: github.com/shahdadk/swiftsign-mcp/issues

License

MIT © Shahdad Kompani