
Convertrilo
io.github.serkandrgnPublished by GitHub account serkandrgnv0.1.2Updated Oct 24, 2026
Create and manage Convertrilo video encoding jobs from MCP clients and agent workflows.
Overview
Lets an assistant create and manage Convertrilo cloud video encoding jobs, including status checks, cancellation, and output delivery.
- What you can do
- Convertrilo exposes a stdio MCP server (convertrilo-mcp) alongside a CLI and TypeScript SDK for the Convertrilo video encoding API. It lets an assistant submit encode jobs from a source URL, S3, or Google Drive, choose codec, resolution, quality, audio and frame-rate policies, and poll job status until completion. It also covers bulk folder ingest, saved encode presets, saved output destinations, job cancellation, file cleanup, and webhook delivery history.
- When to use it
- Use it when an agent or workflow needs to transcode video without building its own encoding pipeline, for example compressing uploads, producing 1080p web MP4s, or queuing one job per video in a storage folder. It suits server-side automation rather than browser apps.
- Requirements
- Runs as a local Node.js process via the npm package @convertrilo/sdk, which targets modern Node.js runtimes with global fetch. A Convertrilo API key is needed, supplied as the CONVERTRILO_API_KEY environment variable or saved locally with convertrilo login or convertrilo init. S3 or Google Drive output requires customer-owned storage credentials or a service account.
Installation
In SourceWeft
- Open Convertrilo in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Convertrilo TypeScript SDK
Type-safe client for the Convertrilo API.
VMAF And Encoding Passes
When optimize: "vmaf" is requested, Convertrilo performs VMAF sampling and one optimized final encode. A supplied passes: 2 value remains accepted for backward compatibility, but the API uses and bills one effective pass.
Pricing responses expose requestedPasses and effectivePasses. New integrations should use passes: 1 with VMAF.
Install
The package currently targets modern Node.js runtimes with global fetch. If your runtime does
not provide fetch, pass fetchImpl to the client.
CLI And MCP Automation
The package includes two executable automation tools:
Use convertrilo for scripts, CI, cron, and local operations. Use convertrilo-mcp
as a stdio MCP server for agent and workflow integrations.
Run convertrilo login or convertrilo init to save an API key locally, or run
convertrilo with no arguments to start the interactive encode wizard. Waiting
commands show terminal progress by default and keep --json clean for scripts.
Shell completion snippets are available with:
See docs/CLI-AND-MCP.md for commands, MCP client config,
S3 output examples, VMAF, two-pass, status, cancel, and balance workflows.
If you want the simplest terminal walkthrough, start with
docs/CLI-QUICKSTART.md.
For agent/client setup, use docs/MCP-QUICKSTART.md.
MCP registry metadata lives in server.json.
Create A Client
Use an API key for server-to-server integrations. Browser apps should call your own backend, then your backend calls Convertrilo.
Examples
The examples/ directory contains starter scripts for the main integration paths:
node-url-to-cdn.ts- encode a public URL and receive a signed CDN download URLnode-url-to-s3.ts- encode a public URL and upload the result to S3/S3-compatible storagegoogle-drive-byo-token.ts- upload output to Google Drive using a customer-owned service accountfolder-ingest-s3.ts- queue one encode job per video in an S3 prefixidempotency.ts- safely retrycreateJobandcreateJobsBulkwebhook-receiver-hmac.ts- verify managed webhook HMAC signatures from a Node receiver
Local SDK smoke tests use .env, but published SDK users should provide credentials through their
own server environment. Do not put Convertrilo API keys or customer storage tokens in frontend code.
For a complete server-to-server walkthrough covering URL, S3, folder ingest, Google Drive
service accounts, polling, and webhooks, see
docs/API-INTEGRATION-GUIDE.md.
Idempotent Job Creation
Use an idempotency key when retrying create calls from your backend. Reusing the same key with the same body returns the original response instead of creating duplicate jobs.
Job File Cleanup
Delete managed upload and output objects after a job reaches a terminal state:
The job record and billing history remain available for auditing. Active jobs return the stable
job_active error until they are canceled.
Saved Encode Presets
Save reusable encode settings without storing source URLs, storage credentials, or output secrets:
Saved Output Destinations
Save reusable delivery targets without storing raw storage secrets in the destination itself. S3 destinations reference an encrypted saved S3 credential:
URL Source To CDN Output
Terminal users can inspect the same report with:
URL Source To S3 Output
For S3-compatible services, pass endpoint and usually forcePathStyle: true.
URL Source To Google Drive Output
For headless API integrations, save a customer-owned Google service account once. Use a Google Shared Drive for output and add the returned service-account email as a member with permission to create files.
Dashboard Google Picker authorization is separate from SDK automation.
Folder Ingest
Queue one job per video in an S3 prefix:
Use maxFiles to cap how many discovered videos are queued from a folder.
Queue one job per video in a Google Drive folder:
Convertrilo mints short-lived Google tokens from the encrypted service-account credential when each worker starts.
Poll each returned jobId with client.onDemandStatus(jobId).
Webhook Delivery History
Managed webhooks are HMAC signed. You can test a webhook and inspect recent delivery attempts:
Regenerate Types
The SDK types are generated from openapi.yaml.
The generate script uses --default-non-nullable false so OpenAPI defaults remain optional
in TypeScript request bodies.
Source: README.md at commit d4ff8b2
Tools
0Version history
1- v0.1.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts