Integration

Zamzar integration

Zamzar converts files between hundreds of formats (documents, images, audio, video, ebooks and more). An agent can look up which target formats a source format converts to and the credit cost, start a conversion from a file reference, a public URL, an (S)FTP or S3 location or an already stored file and wait for it to finish, download the converted files, upload or import files, list and cancel jobs, delete stored files and read the remaining credits. Every conversion spends credits from the Zamzar plan. The API connectivity check is not exposed, and calls go to the production environment, not the free sandbox. Authentication is the Zamzar API key sent as a bearer token.

Connect Zamzar How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Zamzar

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.

File, 4 operations

delete_fileDelete fileDELETEDeletes Zamzar's copy of a file (uploaded, imported or converted) and returns its metadata. The content cannot be downloaded afterwards.
get_fileGet fileGETGets the metadata of a stored file: name, size in bytes, format and creation time. A deleted file answers 404 and an expired one 410.
list_filesList filesGETLists the files stored on Zamzar (uploaded, imported or converted), newest first, 50 per page at most. Expired files are not listed. Page with after or before set to a file id.
upload_fileUpload filePOSTUploads a file reference to Zamzar storage and returns its file id, which start_job accepts as source_file to run several conversions of one file. The file must be in a supported format and within the plan's maximum file size.

Import, 3 operations

get_importGet importGETGets one import: its status (initialising, downloading, successful or failed), the failure reason, and once successful the stored file and its id.
list_importsList importsGETLists the imports (files copied to Zamzar from a URL, (S)FTP server or S3 bucket), newest first, 50 per page at most.
start_importStart importPOSTStarts copying a file from a URL, (S)FTP server or S3 bucket into Zamzar storage and returns the import with status initialising. Check get_import until it is successful; its file.id can then be passed to start_job.

Job, 3 operations

cancel_jobCancel jobDELETECancels a conversion job that has not finished and returns it with status cancelled. Credits are still charged for a job cancelled this way.
get_jobGet jobGETGets one conversion job: status (initialising, converting, successful, failed or cancelled), failure reason, credit cost, source file and target_files whose ids download_file accepts.
list_jobsList jobsGETLists conversion jobs, newest first, 50 per page at most, with each job's status, source file and target files. Limited to 1 call per second.

Conversion job, 2 operations

start_jobStart jobPOSTConverts a file given by URL or by the id of a file stored on Zamzar; download each target_files id with download_file. Spends credits. Waits for the job and returns the finished result; gives up after 10 minutes.
start_job_with_fileStart job with filePOSTConverts a file reference from an earlier step to another format; download each target_files id with download_file. Spends credits. Waits for the job and returns the finished result; gives up after 10 minutes.

Format, 2 operations

get_formatGet formatGETGets one source format with the target formats it converts to and the credit cost of each. Call it before start_job to pick a valid target_format. An unsupported format answers 404.
list_formatsList formatsGETLists the source formats Zamzar converts, alphabetically, each with its target formats and the credit cost of each conversion. 50 per page at most; page with after set to paging.last (a format name).

Account, 1 operation

get_accountGet accountGETGets the account's plan (name, monthly price, conversions per month, maximum file size in bytes) and the production and test credits left in the current billing period.

Content, 1 operation

download_fileDownload fileGETDownloads the content of a stored file, typically a converted file from a job's target_files, and returns it as a file reference.

Successful, 1 operation

list_successful_jobsList successful jobsGETLists only the conversion jobs that finished successfully, newest first, 50 per page at most. Limited to 1 call per second.

Use Zamzar from Claude Code, Cursor or Codex

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

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