Integration

fynk integration

fynk is a contract management and e-signature platform. Create documents (contracts, offers, NDAs) from templates, fill their dynamic fields and metadata, manage parties, signatories, document users and the signing order, move documents through review, signing and done, link related documents, read comments, conditions, stored files and the latest PDF, create or revoke shareable links, clone global templates, and manage tags, metadata fields, teams and document types. Left out: creating documents from an uploaded PDF and storing files (both need an upload to a presigned storage URL outside this API), the PDF download route that answers with a redirect (use get_latest_revision_pdf), and reading back an existing shareable link or changing its expiry or message (those routes return the link URL; delete the link and create a new one instead). Requests use fynk API version 2026-08-25, or the account's default version when that is newer. Authentication is an API token created by an account owner in fynk (Account settings > Integrations > API), sent as a Bearer token; each route needs a token role such as Document Reader or Document Manager.

Connect fynk How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with fynk

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.

Metadata value, 5 operations

add_document_metadata_valueAdd document metadata valuePOSTAdds a metadata field (metadata_uuid from list_metadata) to a document and optionally sets its value, in the format of the field's value_type. Use update_document_metadata_values for several fields at once.
delete_document_metadata_valueDelete document metadata valueDELETERemoves a metadata value from a document. For a metadata that always exists, it is only detached and reset to its default value.
list_document_metadata_valuesList document metadata valuesGETLists the metadata values of a document: each value with its metadata field definition, source (user, AI analysis, computed, dynamic field...) and computed status.
update_document_metadata_valueUpdate document metadata valuePUTChanges the value of one metadata value of a document (its uuid from list_document_metadata_values), in the format of the field's value_type.
update_document_metadata_valuesUpdate document metadata valuesPUTSets or removes up to 20 metadata values of a document in one call: each change names a metadata uuid or name, an operation (set or unset) and, for set, the value. Returns the values that were set.

Document, 4 operations

delete_documentDelete documentDELETEPermanently deletes a document; it cannot be restored. To only hide it from the document lists while keeping its data, use archive_document.
get_documentGet documentGETReturns one document with its stage, signing settings, parties, teams, users, signatories, dynamic fields with their values, metadata values and tags.
list_documentsList documentsGETLists the account's documents with stage, origin, template and parties, filterable by text, stage, origin, tag, team, template, user, discussions and expiry, page by page. Archived documents are left out unless filter[archived] is true.
update_documentUpdate documentPUTUpdates a document's name, signing settings (signature type, sequential signing, invitation message) and document type. Only the fields sent change.

Metadata, 4 operations

create_metadataCreate metadataPOSTCreates a custom metadata field for the account. name (lowercase letters, digits and underscores) and value_type are fixed once created; display_name, description, AI prompt and keywords can change later.
delete_metadataDelete metadataDELETEDeletes a custom metadata field and every value stored for it on documents. System metadata cannot be deleted.
list_metadataList metadataGETLists the account's metadata fields (system and custom) with their type, value type, allowed select values and description. Their uuid or name is what document metadata tools take.
update_metadataUpdate metadataPUTUpdates a custom metadata field's display name, description, AI prompt, keywords, select values or relevant document types. System metadata and the name and value type cannot change.

Signatory, 4 operations

add_signatoryAdd signatoryPOSTAdds a signatory to a document for a party (party_uuid from list_document_parties) by email, with optional name, mobile phone and title. The new signatory goes last in the signing order.
list_signatoriesList signatoriesGETLists a document's signatories with name, email, mobile phone, title, party and signing_order.
remove_signatoryRemove signatoryDELETERemoves a signatory from a document; the person keeps any document access. Removing the last signatory of a party is refused (409) while the document is being signed.
update_signatoryUpdate signatoryPUTUpdates a signatory's party, name, mobile phone or title. For a signatory linked to a fynk account user, only party_uuid and mobile_phone can change.

Tag, 4 operations

create_tagCreate tagPOSTCreates a tag (a label for documents and templates) with a name and a hex color.
delete_tagDelete tagDELETEDeletes a tag from the account.
list_tagsList tagsGETLists the account's tags (labels for documents and templates) with name and color, sortable and paginated.
update_tagUpdate tagPUTRenames a tag or changes its hex color.

User, 4 operations

add_document_userAdd document userPOSTGives a person access to a document as owner, collaborator or viewer. invite_method fynk_email (default) emails an invitation, personal_link returns a personal link instead, none adds them silently.
list_document_usersList document usersGETLists everyone who has access to a document with their access level (owner, collaborator or viewer) and whether they are also a signatory; filter by role.
remove_document_userRemove document userDELETERemoves a person's access to a document, and their signatory status with it. A document keeps at least one owner: removing the last one answers 409.
update_document_userUpdate document userPUTUpdates a document user's access level (role), party or, for people outside the fynk account, name and title. Changing the role never changes signatory status.

Dynamic field, 3 operations

list_document_dynamic_fieldsList document dynamic fieldsGETLists a document's dynamic fields (fillable placeholders) with their type, question, mandatory flag and current value; filter[visibility] keeps only the fields shown, or not shown, in the document.
update_document_dynamic_fieldUpdate document dynamic fieldPUTSets the value of one dynamic field of a document, in the format of the field's type (text, number, "EUR;1234.56" currency, "2025-12-31" date, true or false, a select value...).
update_document_dynamic_fieldsUpdate document dynamic fieldsPUTSets up to 20 dynamic field values of a document in one call. Keys are a field's uuid, ref_uuid or name; values follow the field type format. Returns the fields that changed.

Linked document, 3 operations

link_documentsLink documentsPOSTLinks this document to another one (other_document_uuid) with a relationship such as parent_of, child_of, amendment_to, amended_by, renewal_of or replaced_by. Returns the relationship in normalised form.
list_linked_documentsList linked documentsGETLists the relationships between a document and other documents (parent, amendment, renewal, addition, replacement, termination), each with its controller and peripheral document.
unlink_documentsUnlink documentsDELETERemoves a relationship between two documents, by the relationship uuid from list_linked_documents.

Party, 3 operations

add_document_partyAdd document partyPOSTAdds a party to a document. For an account party send account_party_uuid and reference only; for an external party send reference, entity_name, address and scope.
list_document_partiesList document partiesGETLists a document's parties (the companies or people involved in signing), with reference, entity name, address, scope and whether each is internal or ready to sign.
update_document_partyUpdate document partyPUTUpdates a party of a document (reference, entity name, address, scope). For a party linked to an account party only reference can change.

Comment, 2 operations

get_document_commentGet document commentGETReturns one comment or change proposal made on a document, by its UUID from list_document_comments.
list_document_commentsList document commentsGETLists the comments and change proposals made on a document, with author, scope, resolution status and text, filterable by resolution status (open or resolved), scope and type (comment or proposal).

File storage, 2 operations

get_document_fileGet document fileGETReturns one file of a document's file storage with a temporary, pre-authenticated download_url (it expires shortly; call again for a fresh one).
list_document_filesList document filesGETLists the files kept in a document's file storage: uuid, name, size, MIME type and SHA-256 hash. get_document_file returns a download URL for one of them.

Personal link, 2 operations

create_personal_linkCreate personal linkPOSTCreates a personal link that opens the document as this document user (treat the URL as a secret; fynk sends no email). Only for people outside the fynk account, and not in draft or approved_draft.
delete_personal_linkDelete personal linkDELETEDeletes a document user's active personal link, revoking access for everyone who has the URL. The user stays on the document. Answers 404 when there is no active link.

Public link, 2 operations

create_public_linkCreate public linkPOSTCreates a public link to view the document (anyone with the URL can view it, so treat it as a secret). It expires after 3 months unless expires_at is set (null for never). One active link per document; 409 if one exists.
delete_public_linkDelete public linkDELETEDeletes the document's active public link, revoking access for everyone who has the URL. Answers 404 when the document has no active public link.

Template, 2 operations

get_templateGet templateGETReturns one template with its parties, signatories, dynamic fields, metadata values, tags and signing settings.
list_templatesList templatesGETLists the account's templates with locale, publication status, signature settings and parties; filter by name, locale, status (draft or published), tags, teams or archived.

Archive, 1 operation

archive_documentArchive documentPOSTArchives a document: it is hidden from the document lists (list_documents leaves it out unless filter[archived] is true) and keeps all its data. The document must not be archived already.

Clone, 1 operation

clone_global_templateClone global templatePOSTCopies a global (system-wide) template into the account, published by default so documents can be created from it. terms_confirmed must be true to accept the template's terms (attribution, licence).

Condition, 1 operation

list_document_conditionsList document conditionsGETLists a document's conditions and whether each one currently applies (is_active). Activity follows the document's dynamic field values, so changing a field can change it.

Create from template, 1 operation

create_document_from_templateCreate document from templatePOSTCreates a document from a template (template_uuid from list_templates) with optional name, owners, dynamic field values, party details and signatories. initial_stage signing moves it straight to signing and sends the signatories their invitations.

Document type, 1 operation

list_document_typesList document typesGETLists the document types of the account: fynk's system types and the account's custom ones. Their uuid values go into document_type_uuid on update_document and relevant_document_type_uuids on metadata fields.

Done, 1 operation

move_document_to_doneMove document to donePOSTMoves a document to the done stage, for a document that will not be signed through fynk (signed documents move there on their own). The document must be in draft, approved_draft, review or approved_review.

Global template, 1 operation

get_global_templateGet global templateGETReturns one global (system-wide) template with its author, licence and attribution details. To use it, copy it into the account with clone_global_template.

Me, 1 operation

get_api_token_infoGet api token infoGETReturns the current API token's name, expiry and account, and its API version settings (account default, version of this request, latest available).

Order, 1 operation

set_signing_orderSet signing orderPUTSets the order in which signatories sign: signing_order lists the UUIDs of all the document's signatories in order. Takes effect only before the document moves to signing, and only with sequential signing.

Pdf, 1 operation

get_latest_revision_pdfGet latest revision pdfGETReturns the latest revision of a document as a PDF link: pdf_url is temporary and pre-authenticated (it expires shortly; call again for a fresh one), plus the revision uuid and document name.

Review, 1 operation

move_document_to_reviewMove document to reviewPOSTMoves a document to the review stage to share it with collaborators. From signing or done this cancels the signing process and invalidates any existing signatures.

Signing, 1 operation

move_document_to_signingMove document to signingPOSTMoves a document to signing and sends the invitations to sign (one at a time with sequential signing). The document must be in draft, approved_draft, review or approved_review.

Team, 1 operation

list_teamsList teamsGETLists the account's teams (uuid and name), sortable and paginated. Team UUIDs filter documents and templates.

Unarchive, 1 operation

unarchive_documentUnarchive documentPOSTUnarchives an archived document so it shows in the document lists again. The document must currently be archived.

Use fynk from Claude Code, Cursor or Codex

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

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