About swiftsign
swiftsign is an MCP server for sending and managing e-signature documents from Claude Code. It supports sandbox testing and live sends, with signup and key setup available through tools.
Key features
- 01Create a sandbox account and API key
- 02Send documents or template-based envelopes
- 03Track and list envelope status
- 04Create embedded signing URLs
- 05Void envelopes and upgrade to live sends
Use cases
- 01Test an e-signature flow with a sandbox key
- 02Send contracts to recipients for signing
- 03Check progress or cancel a sent envelope
MCP support
Exposes SwiftSign tools to MCP clients for account signup, document sending, signature tracking, template access, and envelope management.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://swiftsign.ca/mcpclaude mcp add --transport http ca-swiftsign https://swiftsign.ca/mcp{"mcpServers":{"ca-swiftsign":{"type":"http","url":"https://swiftsign.ca/mcp"}}}Open in Cursor{"servers":{"ca-swiftsign":{"type":"http","url":"https://swiftsign.ca/mcp"}}}Open in VS Code{"mcpServers":{"ca-swiftsign":{"type":"http","url":"https://swiftsign.ca/mcp"}}}{"mcpServers":{"ca-swiftsign":{"serverUrl":"https://swiftsign.ca/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
10| Parameter | Type | Required | Description |
|---|---|---|---|
| fields | array | Yes | Signing fields to place on documents |
| confirm | boolean | No | Set true to dispatch immediately on a LIVE key (sk_live_/sk_oat_). Without it, live envelopes are created as DRAFT and returned for human review before anything is emailed. Test keys (sk_test_) always send immediately (sandbox, watermarked). |
| message | string | No | Optional message to include |
| subject | string | Yes | Email subject / document title |
| documents | array | Yes | PDF documents to send |
| recipients | array | Yes | People who need to sign or receive a copy |
Details
From the project READMEswiftsign-mcp
MCP server for SwiftSign — send documents for e-signature directly from Claude Code.
Setup
Add to your .mcp.json (Claude Code config):
{
"mcpServers": {
"swiftsign": {
"command": "npx",
"args": ["-y", "swiftsign-mcp"],
"env": {
"SWIFTSIGN_API_KEY": "sk_your_api_key"
}
}
}
}
Get your API key at swiftsign.ca/dashboard — or skip the browser entirely and call swiftsign_signup to mint a sandbox key (see below).
Test → live keys
SwiftSign keys come in two flavors:
- Sandbox keys start with
sk_test_. Everything works (send, status, templates, embedded URLs) but documents are test sends. No card needed. - Live keys send real, legally binding documents. Upgrade once with
swiftsign_upgrade(a Stripe pay link the dev opens to add a card).
The same tools work in both modes; the mode is determined by the key in SWIFTSIGN_API_KEY.
Agent-native flow (no browser)
An agent can go from zero to a live e-signature without ever opening a dashboard:
swiftsign_signup— create a sandbox account, get ansk_test_key back. Set it asSWIFTSIGN_API_KEY.swiftsign_send_envelope(orswiftsign_send_from_template) — send a test document and watch the full flow work.swiftsign_upgrade— get a Stripe checkout link; the dev opens it once to add a card. Now sends are live.
swiftsign_signup is the only tool that works without a key set — it's how you get one.
Tools
| Tool | Description |
|---|---|
swiftsign_signup | Create a sandbox account and get a test API key (no browser) |
swiftsign_send_envelope | Send document(s) for e-signature |
swiftsign_send_from_template | Send an envelope from a saved template by role |
swiftsign_check_status | Check envelope signing status |
swiftsign_list_envelopes | List all sent envelopes |
swiftsign_list_templates | List your saved templates |
swiftsign_create_embedded_url | Mint a short-lived embedded signing URL |
swiftsign_void_envelope | Cancel an envelope |
swiftsign_upgrade | Get a Stripe pay link to upgrade to PRO (live sends) |
Usage
Once configured, just ask Claude:
"Send this contract to [email protected] for signing"
Claude will use SwiftSign to send the document, place signature fields, and email the recipient a signing link.
Example
"Send the MSA at data/contracts/generated/Acme_MSA.pdf to John Smith ([email protected]) for signing, with a signature field at the bottom"
SwiftSign handles:
- Secure signing link (no account needed for signer)
- E-sign consent (legally compliant)
- Signature capture (draw, type, or upload)
- Document sealing with SHA-256 hash
- Certificate of Completion
- Email notifications to all parties
Legal Compliance
SwiftSign e-signatures are legally binding under:
- Canada: Electronic Commerce Act (Ontario), PIPEDA
- United States: ESIGN Act, UETA
Links
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.