Can I use CloudConvert as a CLI?

Yes. KosmoKrator exposes a CloudConvert CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose CloudConvert through MCP?

Yes. The KosmoKrator MCP gateway can expose selected CloudConvert tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are CloudConvert credentials stored?

CloudConvert credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for CloudConvert MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

files

CloudConvert CLI for Headless Automation

Use the CloudConvert CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 5 read 2 write API key auth

Submit CloudConvert feedback View package source

CloudConvert CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The CloudConvert CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# CloudConvert CLI for Headless Automation
kosmokrator integrations:configure cloudconvert --set api_key="$CLOUDCONVERT_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call cloudconvert.cloudconvert_create_job '{"tasks":"example_tasks","tag":"example_tag","webhook_url":"example_webhook_url"}' --json

Discovery Before Execution

Agents and scripts can inspect CloudConvert docs and schemas before choosing a function.

kosmo integrations:docs cloudconvert --json
kosmo integrations:docs cloudconvert.cloudconvert_create_job --json
kosmo integrations:schema cloudconvert.cloudconvert_create_job --json
kosmo integrations:search "CloudConvert" --json
kosmo integrations:list --json

Useful CloudConvert CLI Functions

Function	Type	Parameters	Description
`cloudconvert.cloudconvert_create_job`	Write	tasks, tag, webhook_url	Create a new CloudConvert job. A job groups one or more tasks (import, convert, export) into a single workflow. Pass a tasks array to define the conversion pipeline.
`cloudconvert.cloudconvert_get_job`	Read	job_id	Get details and status of a CloudConvert job by ID, including all associated tasks and their results.
`cloudconvert.cloudconvert_list_jobs`	Read	per_page, page, status, tag	List CloudConvert jobs with optional filtering by status or tag, and pagination.
`cloudconvert.cloudconvert_create_task`	Write	operation, payload, name, input	Create a standalone CloudConvert task. Specify an operation (e.g., import/url, convert, export/url, capture-website, merge, optimize, thumbnail) and the operation-specific payload.
`cloudconvert.cloudconvert_get_task`	Read	task_id	Get details and status of a CloudConvert task by ID, including the result payload with download URLs for completed conversions.
`cloudconvert.cloudconvert_list_tasks`	Read	per_page, page, status, operation, job_id	List CloudConvert tasks with optional filtering by status, operation, or job ID, and pagination.
`cloudconvert.cloudconvert_get_current_user`	Read	none	Get the authenticated CloudConvert user profile, including remaining credits and subscription info.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related CloudConvert CLI Pages

CI CloudConvert CLI for CI. Cron Jobs CloudConvert CLI for cron jobs. Shell Scripts CloudConvert CLI for shell scripts. Coding Agents CloudConvert CLI for coding agents.