How do I install Swiftsign?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Swiftsign need an API key?

No required environment variable is listed on this record.

What transport does Swiftsign use?

Swiftsign is reached over HTTP.

When was Swiftsign last checked?

Last checked 2026-10-21. E-signatures for agents: mint a sandbox key, send PDFs, track status, download the sealed result.

Swiftsign MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://swiftsign.ca/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http ca.swiftsign-mcp https://swiftsign.ca/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "ca.swiftsign-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://swiftsign.ca/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 0.5.2
Last checked

10 tools

Tools

tools/listVoice mode preview

Tool	What it does
swiftsign_send_envelope	Send a document for e-signature. Accepts PDF as base64, recipients, and field placement. Sandbox keys (sk_test_) send immediately (watermarked test mail). LIVE keys create a DRAFT and return it for human review unless confirm: true — nothing is emailed until confirmed. Field placement: page+x+y (per
swiftsign_confirm_send	Dispatch a DRAFT envelope — use after a human has reviewed an envelope that swiftsign_send_envelope or swiftsign_send_from_template returned as draft_pending_confirmation. This emails the signers. Does NOT work on envelopes already SENT/COMPLETED/VOIDED.
swiftsign_send_from_template	Send an envelope from a saved template by assigning signers to roles. Sandbox keys (sk_test_) send immediately; LIVE keys create a DRAFT for human review unless confirm: true — nothing is emailed until confirmed.
swiftsign_check_status	Check the status of an envelope — who signed, who hasn't, download links. Works in both sandbox (sk_test_ keys) and live.
swiftsign_list_envelopes	List envelopes (sent documents) with their status. Scoped to your key's mode — sandbox (sk_test_) keys see test envelopes, live keys see live.
swiftsign_void_envelope	Cancel/void an envelope that hasn't been completed yet. Signers can no longer sign a voided envelope. Works in both sandbox (sk_test_ keys) and live.
swiftsign_download_signed_pdf	Download the completed, sealed PDF (or its Certificate of Completion) for an envelope. Only works once status is COMPLETED — run swiftsign_check_status first. Does NOT work on DRAFT or SENT envelopes; nothing has been signed yet on those.
swiftsign_upgrade	Initiate the upgrade to PRO ($15/mo flat). Returns a Stripe checkout_url that a human opens once to add a card — agents cannot complete the payment themselves. Moves the account from sandbox (sk_test_) to live sends. Returns status 'updated' if already on the plan.
swiftsign_create_embedded_url	Mint a short-lived embedded signing URL for a recipient (30-minute expiry). Returns a url to embed plus its expiresAt. The envelope must already be SENT. Works in both sandbox (sk_test_ keys) and live.
swiftsign_list_templates	List your saved templates. Scoped to your key's mode — sandbox (sk_test_) keys see test templates, live keys see live.

SwiftSign

AI-native e-signatures. Send, track, and seal contracts from your terminal: Claude Code, Cursor, Zed, or any MCP-aware agent. No drag handles. No per-seat fees.

Why

DocuSign assumes a person with a cursor, dragging signature boxes onto a PDF and paying per seat. SwiftSign assumes code. It is API-first and agent-native: a script or an AI agent can mint a key, send a legally binding contract, track it to completion, and pull back the sealed PDF and Certificate of Completion, end to end, without a browser.

What you get

REST API at /api/v1/envelopes, bearer-token auth, quota-enforced.
MCP server (swiftsign-mcp) with 11 tools so agents can sign documents directly, including agent self-signup and a confirm gate on live sends.
SDKs for JavaScript and Python.
Signer flow with no account required: a secure signing link, e-sign consent, and signature capture by draw, type, or upload.
Sealed PDFs with a SHA-256 hash, full audit trail, and a Certificate of Completion.
DocuSign importer so you can bring existing templates across.
Compliant under ESIGN, UETA (United States), PIPEDA, and the Ontario Electronic Commerce Act (Canada).

Use it from an agent

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

"Send the MSA at ./contracts/Acme_MSA.pdf to [email protected] for signing,
 with a signature field at the bottom."

The agent mints a sandbox key if it has none, places the fields, emails the signer a link, and reports back when it is sealed. See swiftsign-mcp for the full tool list.

Stack

Next.js 16.2 (App Router, Turbopack, React 19)
Prisma 7 + Neon PostgreSQL via @prisma/adapter-pg
Cloudflare R2 (S3-compatible) for PDFs and page images
Resend for transactional email
Stripe for billing (Free / Pro $15 / Team $79, monthly)
Upstash Redis for rate limiting, Sentry for error tracking

Architecture

/api/v1/envelopes: public REST API; bearer-token auth via Authorization: Bearer <apiKey>. Quota enforced (5/mo on Free, unlimited on Pro/Team).
/sign/[token] and /api/sign/[token]: recipient signing flow. No account; the signingToken is the only credential.
/dashboard/*: sender UI. Cookie session via swiftsign_session. Envelopes, billing, settings (API key, sessions), webhooks.
/api/stripe/webhook: Stripe to DB sync (subscription and plan).
/api/cron/webhook-retry: runs every 5 minutes via vercel.json to retry failed outbound webhook deliveries.

Development

git clone https://github.com/shahdadk/swiftsign.git
cd swiftsign
./scripts/bootstrap.sh

The bootstrap script installs the Vercel CLI, logs you in, links the checkout to the SwiftSign Vercel project, pulls production env vars into .env.local, and runs npm install. Then npm run dev and you are operational.

Manual setup:

npm install                  # legacy-peer-deps is pinned in .npmrc (React 19 / Next 16)
npx prisma generate          # writes the Prisma client to src/generated/prisma/
npx prisma migrate deploy    # apply schema migrations to your dev DB
npm run dev                  # dev server on port 3000

Common commands:

npm run dev: start the dev server on port 3000
npm run build: production build (Turbopack)
npm run start: run the built server
npm run lint: ESLint
npx prisma migrate dev --name <slug>: create a new migration
npx tsx prisma/seed.ts: seed a local user

Deploying to Vercel

Provision Neon (PostgreSQL), Cloudflare R2, Resend, Stripe (Pro and Team products plus a webhook on /api/stripe/webhook), Upstash Redis, and Sentry. Set the env vars from .env.local.example on the Vercel project (Production and Preview), connect the repo, and push to main. Vercel runs npx prisma generate and next build. Apply schema once with npx prisma migrate deploy. Verify at /api/healthcheck.

MCP server

The MCP server has its own repository at swiftsign-mcp and is published to npm as swiftsign-mcp.

Swiftsign

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Swiftsign?

Does Swiftsign need an API key?

What transport does Swiftsign use?

When was Swiftsign last checked?

Documentation

SwiftSign

Why

What you get

Use it from an agent

Stack

Architecture

Development

Deploying to Vercel

MCP server