klo for agents

Your agent.
A whole editing room.

Edit video with klo Cloud MCP. Bring footage, describe the cut, and get a finished video back. Your Mac can stay closed.

Connect to klo Cloud

Add a custom remote MCP connector in your agent’s settings. Use this server URL:

https://mcp.getklo.com/mcp

Choose Streamable HTTP and OAuth. Sign in to your own klo account and approve the connection. Compatible clients discover the authorization settings automatically; you don’t need to paste a provider API key into chat.

Editing uses your klo account and available credits. Cloud runs on hosted infrastructure, independently of the Mac app.

Send footage. Ask for the edit.

Attach a video if your agent can share its download with tools, or provide an accessible media link. Then ask:

“Use klo to make a 20-second vertical cut from this footage. Keep the dialogue natural, warm up the color, and add a short animated title. Send me the finished video.”

You can revise the same cloud project afterward: change the pacing, adjust captions, restyle motion, or export another version.

Built for the whole cut

Import footage, arrange and trim a timeline, work with audio and captions, color grade, create editable Remotion graphics, and export a video. Agents can delegate an edit to klo or call editing tools directly.

Cloud and desktop share editing capabilities, but some native Mac effects and masks differ. Cloud projects do not automatically expose local Mac projects or drives.

For agents and developers

  1. Connect to the remote endpoint with the user’s authorization. Discover current schemas with tools/list.
  2. Use list_projects to find an existing project, or create_project for a new one. Keep the returned project ID.
  3. Call add_footage with accessible source URLs or supported file attachments. Wait for get_media to report ready before requesting an edit that depends on that footage.
  4. Call run_klo_agent with the project ID and the user’s brief. For direct edits, use the discovered tools or expand_tools and run_tool.
  5. Follow returned job IDs with get_job, respecting pollAfterSec. An accepted job is not a completed video. Report failures accurately.
  6. Use get_deliverables for finished downloads. Links expire; request fresh links when needed. Use the same project for revisions.

Plain-text operating guide · Connection metadata · OAuth discovery

One plan. Every place you edit.

Your existing Klo plan and credit balance work across the Mac app and Cloud MCP. Connecting another agent does not create another subscription.

Ask your agent “What’s my Klo credit balance?” or “Give me a link to manage my Klo plan.” It can use get_account and get_billing_link to provide your balance and a private Stripe link. You review and complete any purchase in your browser, then return to the conversation.

See current plans. Your agent’s own subscription is separate from Klo.

A few things to know

Files: cloud tools cannot read a path on your laptop. The agent must provide an upload or downloadable URL. Public video links work only when the source permits cloud downloads; restricted sources need the original file.

Privacy: footage sent to Cloud is processed on hosted infrastructure. Account authorization isolates your projects. Signed download links grant access to anyone holding the link, so share them only with the intended recipient.

Timing: editing and rendering run as background jobs and may take minutes, depending on the footage and requested work. Keep checking the returned job status.

Clients: use a client that supports remote MCP and OAuth. Custom connections and public directory listings are separate. Availability in Muse, Grok, or Instinct depends on that platform’s connector support and review; this page does not imply an approved listing.