Integration

swiDOC integration

swiDOC is a Swiss compliant long-term document archive. Upload a file with its metadata (folder path, description, tags, search attributes, retention period), download an archived file, read and update a document's metadata (rename, move to another folder, retag, extend retention), browse the folder tree and list the organization's search attribute definitions. An archived document cannot be deleted before its retention period ends and a retention period can only be extended, so uploads and retention changes are permanent; the API has no delete, search or document-listing route. This is API v2 (multipart upload); the legacy v1 base64 routes are not exposed. Authentication is a personal API key sent as a Bearer token: a Creator or Administrator gets it under Archive, Integrations, swiDOC API, Show API Key, and calls act as that user.

Connect swiDOC How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with swiDOC

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.

Document, 2 operations

download_documentDownload documentGETDownloads an archived document's file by documentId and returns it as a stored file. Use get_document_metadata for its name, folder and retention.
upload_documentUpload documentPOSTArchives one file (max 5 GB) with its metadata and returns result.documentId. Permanent: the document cannot be deleted before its retention period ends.

Document metadata, 2 operations

get_document_metadataGet document metadataGETReturns an archived document's metadata: file name, folder path, description, tags, search attributes, archive date and retention end date.
update_document_metadataUpdate document metadataPATCHUpdates an archived document's metadata: rename, move to another folder (filePath), change description, tags or search attributes, or extend retention. Send only the fields to change. A retention extension is permanent and cannot be undone.

Folder, 1 operation

list_foldersList foldersGETLists the direct child folders of parentId (the archive root folders when left out), limited to folders the key's owner may see, sorted by name. Page with cursor while hasNextPage is true.

Searchattribute, 1 operation

list_search_attributesList search attributesGETLists the organization's search attribute definitions (the names usable in searchAttributes on upload and update). Only active ones unless includeInactive is true.

Use swiDOC from Claude Code, Cursor or Codex

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

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