Integration

Signlift integration

Signlift is a French eIDAS electronic signature API (simple electronic signature with a one-time code by e-mail or SMS, PAdES-sealed PDFs and a proof file). Upload PDFs, create signature requests with signers and stamp placements, let Signlift e-mail the signers or hand them their signing links yourself, follow each request's status, fetch the signed PDFs and the proof file, read the audit log and list branding profiles. Not exposed: registering webhook endpoints, reading the organization's plan and limits, and the health check; a request created through the API cannot be cancelled, and branding profiles are created and edited in the Signlift dashboard only. Authentication is an API key created in the dashboard under Settings, External applications (shown once), sent in the X-Api-Key header; the key alone decides sandbox (watermarked, free) or production (paid plans).

Connect Signlift How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Signlift

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.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

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

Document, 3 operations

get_documentGet documentGETAgents: ask firstReturns an uploaded document's metadata and a pre-signed link to the ORIGINAL unsigned PDF, valid 15 minutes. For the signed PDF use get_signature_request (download_urls).
list_documentsList documentsGETAgents: ask firstLists the PDFs uploaded with the key's environment (sandbox or production), with id, hash, size and status, paginated. Use it to find a document id you did not keep. No download link here: get_document gives one.
upload_documentUpload documentPOSTAgents: ask firstUploads one PDF to Signlift and returns its id, which create_signature_request takes in documents[].id. Signlift computes the file's SHA-256 hash on its side. Any file that is not application/pdf is refused with 422 validation_error.

Signature request, 3 operations

create_signature_requestCreate signature requestPOSTAgents: ask firstCreates an eIDAS simple e-signature request on uploaded documents and returns each signer's signing_url. With send_email true Signlift e-mails the signers itself (the first in sequential mode, all in parallel).
get_signature_requestGet signature requestGETAgents: ask firstReturns a signature request's status, signers and, once finalized is true, fresh 15-minute links to each signed PDF and to the proof file. Wait for finalized, not for status completed.
list_signature_requestsList signature requestsGETAgents: ask firstLists the signature requests of the key's environment, paginated, with status, signers and document ids. Drafts made in the web interface are left out, and download_urls never appear here: use get_signature_request.

Audit log, 1 operation

list_audit_logsList audit logsGETAgents: ask firstReturns the immutable, time-ordered audit log of one signature request (paginated, 20 per page by default: pass limit=100 or page through for a full file). Personal data: signer IP addresses, user agents and OTP destinations.

Branding profile, 1 operation

list_branding_profilesList branding profilesGETAgents: ask firstLists the organisation's branding profiles (signing-flow colours and sender name), sorted by name and paginated: the ids accepted by branding_profile_id. Same profiles for sandbox and production keys; created in the dashboard only.

Use Signlift from Claude Code, Cursor or Codex

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

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