Klo MCP

What klo-mcp MCP server does

The klo-mcp MCP server gives an AI agent control of klo, a native video editor for macOS 13 and later. Its 83 tools cover the workflow from project creation and media import through timeline editing, captions, audio processing, visual styling, generated media, review, and export. Edits are applied to klo’s normal timeline, which a person can open and adjust afterward.

The connector is intended for agents that need to perform concrete video-editing tasks. For example, an agent can remove gaps or filler words, assemble selected takes, add word-level captions, create a vertical version, apply a grade, or export a ProRes file. The available operations include timeline changes such as trimming, splitting, moving, ripple deletion, gap closing, linking, and audio separation.

How the klo-mcp MCP server works

Media stays on the Mac. Rather than sending video bytes through the model context, the agent expresses operations against klo’s local timeline and receives smaller responses, including transcripts, timecodes, and captured frames when visual inspection is needed. This design supports iterative editing without passing the source footage through the MCP conversation.

The server is disabled until enabled in klo’s settings. When enabled, it listens on 127.0.0.1 and requires a bearer token. The preferred HTTP port is 41720, but klo can choose another port if that port is unavailable; the connection URL shown in klo’s settings is authoritative. The klo-mcp MCP server can also run as a stdio package through npx, with authentication supplied through an environment variable.

Setup and configuration

Install klo on a Mac running macOS 13 or newer, then open Settings → Connections and enable the connection. Copy the URL and token displayed there. For HTTP clients, use that URL with an Authorization bearer header. For stdio clients, run the npm package with npx and set KLO_MCP_TOKEN to the copied token.

Claude Desktop can be configured by opening the supplied klo.mcpb package. Claude Code can be added with an HTTP MCP command, while Cursor, Codex, and other MCP clients can use either the HTTP endpoint or the stdio configuration. If the app is running but connections fail, confirm that the bridge is enabled and that the current token and URL match the values in klo’s settings.

Tools and capabilities

The tool groups support:

• Project and library operations, including new projects, file listing, media import, URL import, and source relinking.
• Timeline editing, markers, track locks, in/out points, seeking, and timeline verification.
• Captions, text, fonts, motion templates, transitions, transforms, speed, opacity, blending, and LUTs.
• Audio analysis and editing, including volume envelopes, ducking, beat-based cut quantization, voice isolation, and mix measurement.
• Transcript retrieval, repeated-take detection, footage surveys, frame capture, reference analysis, notes, and style profiles.
• Generated music, sound effects, voiceover, video, spoken-line fixes, and video export.

Generation tools consume credits from the klo account, while timeline control is free with the agent’s own model. The agent is told the price before a paid generation action is taken.

Limitations and notes

The connector requires klo and a compatible Mac; it is not a standalone video editor or an ffmpeg wrapper. It only accepts connections when the in-app bridge is turned on, and its local endpoint is restricted to 127.0.0.1. Rotate the bearer token from klo’s settings when needed.

The tool set is versioned with the klo app’s major and minor releases, so available behavior may track the installed app version. Voice-cloning operations are gated by consent in the app. New accounts receive 10 free asks, while generated media uses account credits; ordinary timeline driving does not use those credits.