Integration

SignWell integration

SignWell is an e-signature service. Create documents for signature from uploaded files or from templates (as drafts or sent at once), send drafts, remind signers, change unsigned recipients or their passcodes, read a document's status and fields, get a download link for the completed PDF and, for Mexico, the NOM-151 certificate; manage templates, webhooks, bulk sends from a CSV, API Applications (read and delete) and account settings. SignWell has no route to list documents or templates. Documents sent outside test mode count toward SignWell API billing. Rate limit: 100 requests per minute per token, 30 per minute for creating documents or templates, 20 per minute in test mode. Authentication is a SignWell API token (Settings, API) sent in the X-Api-Key header.

Connect SignWell How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in SignWell.Built from the 28 SignWell tools below, on the connection you add once.

What you can do with SignWell

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Document, 6 operations

create_documentCreate documentPOSTCreates a document for signature from files (URL or base64) with recipients and fields. draft=true keeps it unsent; draft=false emails or texts every recipient immediately. Returns the document with its id and signing links.
create_document_from_templateCreate document from templatePOSTCreates a document from one template (template_id) or several (template_ids), filling placeholders with recipients and optional template_fields values. draft=true keeps it unsent; draft=false sends it immediately.
delete_documentDelete documentDELETEDeletes a document; if signing is in progress it is canceled for every recipient. Cannot be undone.
get_completed_pdf_urlGet completed pdf urlGETReturns file_url, a download link for a completed document's PDF (or ZIP). The document must be completed (check status with get_document).
get_documentGet documentGETReturns one document with its status, recipients (with signing links and SMS delivery state), fields and their values, files and settings. Use it to check whether a document is completed before get_completed_pdf_url.
send_documentSend documentPOSTSends a draft document (created with draft=true) to its recipients for signing, optionally changing its settings first. Recipients are notified immediately; billed unless test_mode is true. subject and message apply to email only.

Bulk send, 4 operations

create_bulk_sendCreate bulk sendPOSTCreates a bulk send: one document per CSV row, built from templates and SENT to the recipients at once (billed). Check the CSV first with validate_bulk_send_csv.
get_bulk_sendGet bulk sendGETReturns one bulk send with its status, document counts (total, completed, not completed) and templates.
list_bulk_sendsList bulk sendsGETLists bulk sends, 10 per page by default (limit up to 50); next_page gives the following page. Admins and managers can list another user's bulk sends with user_email.
validate_bulk_send_csvValidate bulk send csvPOSTChecks a bulk send CSV's structure and data against the templates, without sending anything, and returns validation errors if any.

Template, 4 operations

create_templateCreate templatePOSTCreates a reusable template from files, with placeholders (signer roles such as Client) and fields assigned to placeholders. draft=false (default) marks it Available for creating documents; nothing is sent.
delete_templateDelete templateDELETEDeletes a template. Cannot be undone.
get_templateGet templateGETReturns one template with its placeholders, fields (with api_ids usable as template_fields in create_document_from_template), files and settings.
update_templateUpdate templatePUTUpdates a template's name, email text, settings, labels, checkbox groups or conditional rules. Only the fields sent are changed; leave a field out to keep its current value. Files, placeholders and fields cannot be changed here.

Webhook, 3 operations

create_webhookCreate webhookPOSTRegisters a callback URL that SignWell POSTs document events to (created, sent, viewed, signed, completed, declined, expired, bounced, SMS failures...). Returns the webhook id, which is also the key to verify each event's hash.
delete_webhookDelete webhookDELETEDeletes a webhook; SignWell stops posting events to its URL.
list_webhooksList webhooksGETLists the webhooks registered on the account, with their callback URLs. The webhook id is also the HMAC-SHA256 key SignWell signs each event hash with.

Account, 2 operations

get_accountGet accountGETReturns the account's name, logo URL, plan tier and default preferences (date format, link expiry, signature options, time zone, recipient language).
update_accountUpdate accountPUTUpdates the account name, logo, time zone, default date format or recipient language. Only the fields sent are changed; leave a field out to keep its current value.

Api application, 2 operations

delete_api_applicationDelete api applicationDELETEDeletes an API Application from the account. Cannot be undone.
get_api_applicationGet api applicationGETReturns an API Application's name, callback URLs, owner and embedded branding preferences.

Recipient, 2 operations

update_authenticationUpdate authenticationPATCHChanges the passcode or passcode delivery of recipients who have not started signing on a sent document. Recipient ids come from get_document.
update_recipientsUpdate recipientsPATCHChanges the name, email, message or passcode of recipients who have not started signing on a sent document (status sent, viewed, pending or bounced). Updated recipients get a new notification email (non-embedded documents).

Bulk send csv template, 1 operation

get_bulk_send_csv_templateGet bulk send csv templateGETReturns data, the base64 of a blank CSV whose columns are the recipient data the given templates need (columns read [placeholder name]_[field label], e.g. customer_address). Fill it for create_bulk_send.

Bulk send document, 1 operation

list_bulk_send_documentsList bulk send documentsGETLists the documents a bulk send created, with each document's status and recipients, 10 per page by default (limit up to 50); next_page gives the following page.

Certificate, 1 operation

get_nom151_certificateGet nom151 certificateGETFor a completed document in a workspace with NOM-151 compliance (Mexico): returns file_url, a link to the certificate ZIP, or with object_only=true the certificate data itself. Answers 422 when no certificate exists.

Reminder, 1 operation

send_reminderSend reminderPOSTSends a reminder now to recipients who have not signed a sent document yet, by email, SMS or both per their delivery method. Leave recipients out to remind all of them.

User, 1 operation

get_current_userGet current userGETReturns the user, membership role, account or workspace (plan tier, template limits, active users) and contact record behind the API token.

Use SignWell from Claude Code, Cursor or Codex

Connect SignWell in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its SignWell operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect SignWell

Create your workspace
Sign up free. Nothing to install.
Connect SignWell once
Add your SignWell connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.