Can Lyro start a file conversion in CloudConvert?

Not with this toolkit. The only task actions it exposes are exports - Create Export S3 Task and Create Export Google Cloud Storage Task - which move a finished result into your storage. Conversions are started elsewhere, and Lyro handles discovery, monitoring, export, and webhooks around them.

How long do conversion results stay retrievable?

Tasks are deleted automatically 24 hours after they complete, so List Tasks stops returning a job and its output URLs once that window passes. Exporting to S3 or Google Cloud Storage is how a result outlives it.

What permissions do the export tasks need?

For S3, the AWS credentials need s3:PutObject, plus PutObjectAcl if a non-default ACL is used. For Google Cloud Storage, the service account needs write access to the bucket. Show User separately requires the user.read scope, which is what Lyro uses to confirm authentication.

Whose conversion credits do these calls draw on?

The account behind the CloudConvert credentials you connect. Show User returns that account's ID, username, email, and remaining conversion credits, so Lyro can report the headroom left before a large batch is queued rather than after a job stops.

Cloudconvert MCP integration

Checks which conversions and engine options exist, exports finished files to S3 or Google Cloud Storage, tracks task status, and manages job webhooks.

Connect Cloudconvert See all integrations

9actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Create export s3 task
Lyro converts a file and exports the result directly to your Amazon S3 bucket, automating large-batch processing. Runs asynchronously without local storage.
Create export google cloud storage task
Lyro converts a file and uploads the result to Google Cloud Storage, enabling automated pipelines and cloud-native workflows. No local download needed.
List tasks
Lyro displays all of your CloudConvert conversion tasks with status, input/output details, and results. Useful for tracking batch jobs and debugging.

See all 9 actions

How businesses use Cloudconvert + Lyro

Each card is one request a support team gets, and the Cloudconvert actions Lyro runs to close it.

Confirm a conversion is possible before promising it
Lyro lists the supported formats with their engines and options, and the operations available for a given input and output pair, so a question about whether CloudConvert handles a format is answered from the API.
List Supported FormatsList OperationsList Tasks
Send finished files to your own storage
Rather than leaving output on a temporary URL, Lyro creates an export task that writes the result into an S3 bucket or a Google Cloud Storage bucket with the credentials already configured for it.
Create Export S3 TaskCreate Export Google Cloud Storage TaskList Tasks
Track a job through to finished or failed
Lyro lists tasks by status or job ID, pulls output file URLs from the ones that finished, reads the error code on the ones that did not, and checks the operation's own requirements when a payload was rejected.
List TasksList OperationsList Supported Formats
Get notified instead of polling
Lyro registers a webhook for job created, finished, and failed events, lists the ones already in place, and removes any pointing at an endpoint that is no longer in use.
Create WebhookList WebhooksDelete Webhook

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Cloudconvert actions it has and picks the ones a request needs.

01
Connect Cloudconvert
Authorize the Cloudconvert account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Cloudconvert actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Cloudconvert · Lyro

Everything else about Cloudconvert

Setup, permissions, and the limits of what Lyro can do inside Cloudconvert.

Not with this toolkit. The only task actions it exposes are exports - Create Export S3 Task and Create Export Google Cloud Storage Task - which move a finished result into your storage. Conversions are started elsewhere, and Lyro handles discovery, monitoring, export, and webhooks around them.

Every action available in Cloudconvert

All 9 actions your agent can call on Cloudconvert, straight from the live MCP connection.

Create export google cloud storage task
Create a task to export files to a Google Cloud Storage bucket.
Create export s3 task
Create a task to export files to an Amazon S3 bucket.
Create webhook
Creates a new webhook to receive CloudConvert event notifications.
Delete webhook
Permanently delete a webhook by its ID.
List operations
List all possible CloudConvert operations with their available options and engine details.
List supported formats
List all supported conversion formats, engines, and options.
List tasks
List all CloudConvert tasks with their status, payload and results.
List webhooks
List all webhooks.
Show user
Retrieves the current authenticated user's CloudConvert account information.