Integration

Stiply integration

Stiply is a Dutch electronic signature service. Send documents (by URL) to one or more signers for signing in parallel or in sequence, with signature, initial, text, date, checkbox or radio fields and optional SMS, iDIN or e-mandate identification; list and look up sign requests, follow their progress and signers, send reminders, extend the term, cancel or delete them, and download the signed documents, the proof document and the files signers uploaded; read usage totals per account or organization. Stiply deletes signed documents and their data after one month, at the end of the month, so download what you need to keep. Authentication is a Bearer token in the Authorization header: a Personal Access Token created in Stiply's API settings (it expires on the date you choose), or OAuth2 with the SignRequest.ReadWrite scope. Stiply allows at most 300 requests per minute.

Connect Stiply How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Stiply

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.

Sign request, 7 operations

cancel_sign_requestCancel sign requestPOSTCancels a sign request, optionally notifying the signers with a message. A canceled sign request is deleted automatically after at most 90 days.
delete_sign_requestDelete sign requestDELETECancels and deletes a sign request at once. Signers are NOT notified; use cancel_sign_request to inform them.
extend_sign_request_termExtend sign request termPOSTExtends the term of a sign request by a period such as 1d, 2w or 3m, giving it a new expiration. Signers are informed of the new expiration by default.
get_sign_requestGet sign requestGETReturns one sign request by id: title, key, external_key, status, sent, expiry, signed and cancel dates, owner and signers.
get_sign_request_by_keyGet sign request by keyGETReturns a sign request looked up by a key instead of its numeric id. Stiply documents this one route for both the external_key you set in send_sign_request and the sign request's own key.
list_sign_requestsList sign requestsGETLists the sign requests the user may see in their default account, 100 per page at most, optionally filtered by status and sorted with $orderby. Not available with the SignRequest.ReadWrite.Limited scope.
send_sign_requestSend sign requestPOSTCreates a sign request from documents given by URL and sends it to the signers, who are emailed a signing link unless their invitation_method is custom. Returns the sign request with its id, key, status and signers.

Signer attachment, 4 operations

download_all_signer_attachmentsDownload all signer attachmentsGETDownloads every file one signer uploaded for a sign request.
download_signer_attachmentDownload signer attachmentGETDownloads the file a signer uploaded for one requested attachment.
get_signer_attachmentGet signer attachmentGETReturns one requested signer attachment: its signer id, description, whether it is optional, whether a file has been uploaded, and identity card information when applicable.
list_signer_attachmentsList signer attachmentsGETLists the files the signers of a sign request were asked to upload: id, signer id, description, whether it is optional and whether it has been uploaded.

Document, 2 operations

download_document_fileDownload document fileGETDownloads one document of a sign request as a PDF file.
list_sign_request_documentsList sign request documentsGETLists the documents of a sign request: id, filename, name, size, MIME type and download_url.

Signer, 2 operations

get_signerGet signerGETReturns one signer of a sign request: email, name, role, sign_url, redirect_url, reject reason, fields, attachments, progress and identification results (iDIN, e-mandate).
list_signersList signersGETLists the signers of a sign request with their id, email, name, role, language, authentication method, sign_url (the link to send them yourself when the invitation method is custom), fields and recorded progress.

Usage report, 2 operations

get_account_usageGet account usageGETReturns usage totals of one Stiply account over a date range (default: month start to today): documents sent, SMS sent, iDIN, iDIN Complete and e-mandate transactions started, batch documents sent, documents merged and sealed.
get_organization_usageGet organization usageGETReturns usage totals summed over every account of a Stiply organization for a date range (default: start of the current month to today), with the same counters as get_account_usage.

Progress, 1 operation

list_sign_request_progressList sign request progressGETReturns the audit trail of a sign request: each recorded action with its time, IP address, location, user agent, extra value and email status.

Proof document, 1 operation

download_proof_documentDownload proof documentGETDownloads the proof document of a completed sign request, the file that records how and when each signer signed.

Reminder, 1 operation

send_sign_request_reminderSend sign request reminderPOSTSends a reminder email to the signer or signers whose turn it is to sign the sign request.

Sign request file, 1 operation

download_sign_request_filesDownload sign request filesGETDownloads a zip file with all the documents of a sign request; once the sign request is completed, the zip also holds the proof document.

Use Stiply from Claude Code, Cursor or Codex

Connect Stiply in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Stiply 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 Stiply

Create your workspace
Sign up free. Nothing to install.
Connect Stiply once
Add your Stiply 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.