Integration

SlashedCloud Video Encoding integration

SlashedCloud Video Encoding (venc.slashed.cloud) transcodes videos stored in the storage connected to your encoding service. An agent can queue an encoding process for one source video with a list of jobs (encode to H.264, H.265 or AV1 MP4, preview clips, storyboard sprites, screenshots, each with optional resize, trim, crop or watermark steps), follow its status, read its detailed result with output files and credit cost, and requeue processes. Encoding is billed per second of encoded video, with multipliers for resolution, codec (AV1 costs 5 times H.264), frame rate and priority. Storage and services are configured in the SlashedCloud dashboard. SlashedCloud's batch and on-the-fly image services use other hosts and keys and are not covered. Authentication is the service's secret key, sent as a Bearer token.

Connect SlashedCloud Video Encoding How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in SlashedCloud Video Encoding.Built from the 4 SlashedCloud Video Encoding tools below, on the connection you add once.

What you can do with SlashedCloud Video Encoding

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.

create_encoding_processCreate encoding processPOSTQueues a billed encoding process for one source video and returns its process_id at once. Poll get_process_status until FINISHED or a failed status, then read get_process_details for output files and cost.
get_process_detailsGet process detailsGETReturns an encoding process in full: status, credit cost, the probed source video, and each job with its output file path, size, codecs, dimensions and timings. Use it once get_process_status is final.
get_process_statusGet process statusGETReturns an encoding process status and when it last changed. Pending: RECEIVED, VALIDATING, ENQUEUED, PROCESSING. Final: FINISHED, or REJECTED, FAILED, FAILED_BILLING, PARTIALLY_FAILED with fail_message.
retry_processesRetry processesPOSTRequeues existing encoding processes so they are processed again (encoding work is billed per encoded second). Returns one result per process id: status 200 with the attempt number, or 404 when no process has that id.

Use SlashedCloud Video Encoding from Claude Code, Cursor or Codex

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

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