Agents and automation

Version 1.30.0

Two MCP servers are available. The full server at /mcp holds every tool. The Tvarka Proof server at /mcp/proof holds eight tools. It can never send a document for signature. It suits an agent that only needs proofs.

Connect an agent

Add the server address in the agent settings. The person signs in once and allows the connection. The agent then works in that workspace.

BASE=https://sign-api.tvarka.pro
# TVARKA_KEY holds your API key.
curl -sS "$BASE/mcp/proof" \
  -H "Authorization: Bearer $TVARKA_KEY" -H 'Content-Type: application/json' \
  -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}'

Integrations: Google Workspace, MCP and n8n

Connector overview and setup guides: tvarka.eu/integrations/.

Google Workspace (Google Docs and Google Drive)

Install Tvarka Sign on Google Workspace Marketplace for individual or domain-wide administrator deployment. Send active Google Docs™ or selected Google Drive™ files for simple e-signature or eIDAS qualified signature directly from the sidebar, track per-signer status, download the evidence ZIP, and save completed signed PDFs back into your Tvarka Sign folder in Google Drive™. Connect your workspace once with Tvarka sign-in (no API key pasted into the card). Setup guide: tvarka.eu/google-workspace/.

n8n integration

Install n8n-nodes-tvarka-sign in self-hosted n8n through Settings → Community Nodes. Follow the maintained installation and credential guide and import the example workflow.

The connector uploads files, creates hosted qualified-signing requests, reads or lists them, downloads results, cancels requests and sends reminders. Use a Sign workspace key; DD and ATK keys are separate. It does not start headless signatures or the web application's simple e-signatures. Request creation is not signature completion.

The example needs your credentials and an uploaded file token. It explicitly sends email invitations, waits between status checks and downloads only after completion. Replace its example inputs before running; protect execution data and ceremony links. Existing sandbox keys simulate and return a sandbox-marked download. n8n Cloud installation requires n8n verification; npm publication alone does not establish Cloud availability.

Contract

Endpoints

MCP server

Tvarka Sign 1.21.0, Streamable HTTP at /mcp, registry name pro.tvarka/sign. Documents come from the workspace vault, Markdown text, a link, a chat attachment or base64. See Agents: Claude, ChatGPT, Gemini, Copilot for one-click OAuth setup.

Agents: Claude, ChatGPT, Gemini, Copilot

Connect Tvarka Sign to your assistant once; then ask it to send a document for signature, track it and fetch the signed original. Server URL: https://sign-api.tvarka.pro/mcp. The assistant opens a Tvarka page, you confirm with your eID, choose the company and allow the connection. It then acts as you, with your rights in that company, and signatures are billed to the company as usual. No key is pasted anywhere.

What the assistant can do: write the document as text and have Tvarka render it to PDF/A, send a PDF from a link or a chat attachment, add you as the first signer, set a signing order and deadlines, remind, add signers, cancel, and hand you a download link for the signed document. It never signs: every signature is a person with their own eID. Connections are listed, with last use, under Settings, API settings, Connected apps, and end with one click.

Related pages

Questions: info@tvarka.pro