Get started free
All integrations

CloudConvert integration

CloudConvert file conversion API: assemble jobs that chain import, convert and export tasks across more than two hundred file formats, follow the progress of every task, and read the temporary download URL of each produced file. Work is asynchronous, so a job is accepted immediately and its tasks move through waiting and processing before they finish. This integration covers jobs, tasks, the standalone import, convert and export task endpoints, the blocking wait endpoints and the account credit balance.

16 toolsTokenAPI docs

Common CloudConvert use cases

  • inspecting each step of a job
  • getting an export URL in one step
  • converting a small file in one step
  • converting an imported document to PDF
  • converting an uploaded document to PDF
  • finding a recent conversion by its tag
  • waiting for an individual conversion step
  • retrieving the PDF produced by a conversion
  • recovering from a transient conversion failure
  • stopping a conversion that is no longer needed

What you can do with CloudConvert

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.

Task, 10 operations

  • POSTcancel_task

    Cancels a CloudConvert task that is still waiting or processing.

  • POSTcreate_convert_task

    Converts a file already inside CloudConvert into another format.

  • POSTcreate_export_url_task

    Turns a converted file into a temporary download URL.

  • POSTcreate_import_upload_task

    Opens a signed upload slot so file bytes can be pushed into CloudConvert.

  • POSTcreate_import_url_task

    Imports a file into CloudConvert by downloading it from a public URL.

  • DELETEdelete_task

    Deletes a CloudConvert task together with its output file.

  • GETget_task

    Reads the status and the result of a single CloudConvert task.

  • GETlist_tasks

    Lists CloudConvert tasks with optional job, status and operation filters.

  • POSTretry_task

    Retries a CloudConvert task that ended in error.

  • GETwait_for_task

    Waits for one CloudConvert task to finish instead of polling it.

Job, 5 operations

  • POSTcreate_job

    Starts a CloudConvert job that imports, converts and exports one or more files.

  • DELETEdelete_job

    Deletes a CloudConvert job together with its files.

  • GETget_job

    Reads the current status of a CloudConvert job and of every task inside it.

  • GETlist_jobs

    Lists CloudConvert jobs with optional status and tag filters.

  • GETwait_for_job

    Waits for a CloudConvert job to finish instead of polling it.

User, 1 operation

  • GETget_current_user

    Reads the CloudConvert account and how many conversion credits are left.

Use CloudConvert from Claude Code, Cursor or Codex

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

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect CloudConvert once

    Add your CloudConvert connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. 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.

CloudConvert integration FAQ

What can you do with the CloudConvert integration?
LiveContext exposes 16 operations on CloudConvert, covering task, job and user. Common uses include inspecting each step of a job, getting an export URL in one step and converting a small file in one step.

Popular integrations

Browse the whole catalog