Swiftsign MCP server
{
"mcpServers": {
"swiftsign": {
"type": "http",
"url": "https://swiftsign.ca/mcp"
}
}
}{
"mcpServers": {
"swiftsign": {
"type": "http",
"url": "https://swiftsign.ca/mcp"
}
}
}{
"mcpServers": {
"swiftsign": {
"type": "http",
"url": "https://swiftsign.ca/mcp"
}
}
}{
"servers": {
"swiftsign": {
"type": "http",
"url": "https://swiftsign.ca/mcp"
}
}
}{
"mcpServers": {
"swiftsign": {
"type": "http",
"url": "https://swiftsign.ca/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.5.2
What it does
SwiftSign exposes an e-signature service via REST API and MCP tools, letting agents and scripts send PDFs for signing, track status, and download sealed documents. It is for developers building contract workflows into code or AI agents, without per-seat licensing.
- Send a PDF contract to signers via email and retrieve the signed document once completed.
- Automate contract signing workflows in an AI agent or script with no browser interaction required.
- Retrieve sealed PDFs with audit trails and Certificates of Completion for compliance records.
Tools this server exposes
| Tool | Does |
|---|---|
| mint_sandbox_key | Create a sandbox API key for testing. |
| send_envelope | Send a PDF to one or more signers with signature field placement. |
| get_envelope_status | Check the signing status of a sent document. |
| download_sealed_pdf | Retrieve the signed and sealed PDF after completion. |
| list_envelopes | List all sent envelopes and their statuses. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.