Integration

IgniSign integration

IgniSign is a European electronic signature API (simple and advanced signatures, seals and timestamped log capsules). Create signature requests in one call or step by step (draft, documents, signers, publish), upload the files to sign or set JSON or hash-only content, manage signers and read signer profiles, follow requests and download the original files, signature images and signature proofs (the signed PDF), check that a file is the one that was signed, and manage webhook endpoints and their events. Sending or publishing a request invites its signers: with a PRODUCTION key their signatures are legally binding and billed, while a DEVELOPMENT key simulates them. Console user invitations, signer secret regeneration, machine-to-machine seals (they need a hash signed with your private key), bare signatures (their own OAuth flow), low-level per-signer proofs and the batch status read are not exposed. Authentication is an API key (it starts with skv2_) sent as a Bearer token; a key belongs to one application and one environment, so the connection also asks for the application ID (appId_...) and the environment in capitals (DEVELOPMENT, STAGING or PRODUCTION) the key was created for in the IgniSign console. Both can be read in the key itself, skv2_<environment>_<id>_..., the application ID being appId_<id>.

Connect IgniSign How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with IgniSign

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.

Webhook, 4 operations

create_webhookCreate webhookPOSTRegisters a webhook endpoint: IgniSign sends signature request, signer, document and proof events to this URL.
delete_webhookDelete webhookDELETERemoves a webhook endpoint.
list_webhooksList webhooksGETLists the webhook endpoints registered for the connected application and environment.
update_webhookUpdate webhookPUTUpdates a webhook endpoint's URL or description.

Context, 3 operations

get_application_contextGet application contextGETReturns the context of the connected IgniSign application: its name, type (SIGNATURE, SEAL or LOG_CAPSULE), status, per-environment settings, and the signer profiles and signature profiles it defines.
get_document_contextGet document contextGETReturns a document with its context: statements to accept and a signature summary per signer.
get_signature_requestGet signature requestGETReturns a signature request with its full context: status, title, documents, signers and their status, statements and the signature proof status and URL.

Document, 3 operations

delete_documentDelete documentDELETERemoves a document from its draft signature request.
get_documentGet documentGETReturns a document's information: label, file name, size, MIME type, hash, status and the signature request it belongs to.
update_documentUpdate documentPUTUpdates a document's label, description or external id.

Signature request, 3 operations

create_signature_requestCreate signature requestPOSTCreates an empty draft signature request and returns its signatureRequestId. Then add documents (create_document), set title, documents and signers (update_signature_request) and send it with publish_signature_request.
list_signature_requestsList signature requestsGETLists the signature requests of the connected application and environment, one page at a time, with their status, title, documents and signers.
update_signature_requestUpdate signature requestPUTUpdates a draft signature request: title, description, documents, signers, approvers, recipients of the signed copy, expiration date, language, diffusion mode and signature method.

Signer, 3 operations

create_signerCreate signerPOSTCreates a signer in a signer profile, or updates the existing one when the signer is already known (alreadyExists in the answer). The fields required depend on the signer profile (see get_signer_profile_inputs).
get_signerGet signerGETReturns a signer summary: name, email, status, external id, signer profile and the inputs already provided.
update_signerUpdate signerPUTUpdates a signer's data (name, email, phone number, nationality, birth data, external id or signer profile).

Event, 2 operations

get_webhook_eventGet webhook eventGETReturns one webhook event: topic, action, content sent, delivery status, error and the endpoint's response.
list_webhook_eventsList webhook eventsGETLists the events sent to a webhook endpoint, with their topic, action, delivery status and the endpoint's answer, filtered by delivery result and one page at a time.

File, 2 operations

download_original_documentDownload original documentGETDownloads the original file of a document, as it was before signature, and stores it as a file.
upload_document_fileUpload document filePOSTUploads the file (a PDF or other file) of a document in a draft signature request; the document then carries its name, size, MIME type and hash.

Signer profile, 2 operations

get_signer_profileGet signer profileGETReturns one signer profile: its name, status, integration mode, signature authentication methods and the signers attached to it.
list_signer_profilesList signer profilesGETLists the signer profiles of the connected application and environment. A signer profile sets which identity data and authentication a signer needs; its id is used by create_signer.

Check authenticity, 1 operation

check_document_authenticityCheck document authenticityPOSTUploads a file and checks whether it is the exact file that was signed for this document; returns authenticityValidated true or false.

Close, 1 operation

close_signature_requestClose signature requestPOSTCloses (cancels) a signature request; signers can no longer sign it.

Content, 1 operation

delete_document_contentDelete document contentDELETERemoves the content (file, JSON data or private hash) of a document in a draft signature request, keeping the document itself.

Data json content, 1 operation

set_document_json_contentSet document json contentPOSTSets a document's content to JSON data (a structured document signed as data rather than as a file).

Detail, 1 operation

get_signer_detailsGet signer detailsGETReturns a signer with details: the summary fields plus the signer's claims and the latest signature requests the signer is part of.

Img signature, 1 operation

get_signature_imagesGet signature imagesGETReturns the images (base64) of the signatures placed on a document, one per signer.

Init document, 1 operation

create_documentCreate documentPOSTCreates an empty document attached to a draft signature request and returns its documentId. Give it content next with upload_document_file, set_document_json_content or set_document_private_hash.

Inputs needed, 1 operation

get_signer_profile_inputsGet signer profile inputsGETReturns which signer fields (first name, last name, email, phone number, birth data...) a signer profile requires and which are optional, to know what create_signer must be given.

Log capsule, 1 operation

create_log_capsuleCreate log capsulePOSTCreates a log capsule: IgniSign timestamps a SHA-256 hash you send (base64) and returns the hash with its timestamp token, as proof that the data existed at that time. Requires a LOG_CAPSULE application.

One call sign, 1 operation

create_signature_request_one_callCreate signature request one callPOSTCreates and sends a signature request in one call: IgniSign invites each signer (email, names, signer profile) to sign the documents (base64 or URL). With a PRODUCTION key these are real, legally binding, billed signatures.

Private content, 1 operation

set_document_private_hashSet document private hashPOSTSets a document's content to the SHA-256 hash of a file you keep private: the file itself is never sent to IgniSign.

Publish, 1 operation

publish_signature_requestPublish signature requestPOSTPublishes a draft signature request so IgniSign invites its signers to sign; returns the signers and, in embedded mode, their session tokens. With a PRODUCTION key these are real, legally binding, billed signatures.

Resend, 1 operation

resend_webhook_eventResend webhook eventPOSTSends a webhook event to its endpoint again.

Revoke, 1 operation

revoke_signerRevoke signerDELETERevokes a signer, who can no longer take part in signature requests.

Signature proof, 1 operation

download_signature_proofDownload signature proofGETDownloads a signed document's signature proof of the given type (PDF_WITH_SIGNATURES is the signed PDF) and stores it as a file. Available once the signature request is completed.

Signers paginate, 1 operation

list_signersList signersGETLists the signers of the connected application and environment, one page at a time, with the total count.

Signers search, 1 operation

search_signersSearch signersGETSearches the signers of the connected application and environment with a text filter and returns the matching signers and their total count.

Use IgniSign from Claude Code, Cursor or Codex

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

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