Mcpcut

What mcpcut does

The mcpcut MCP server gives an MCP-capable agent access to Orccut, a timeline-based video editor for agent-driven workflows. It models a project as a set of timeline snapshots and records named editing operations in a journal. This lets an agent make changes while a person reviews or adjusts the same project through the Orccut browser editor.

The tool surface covers the main stages of a video workflow. Agents can create and inspect projects, add media from HTTP or HTTPS URLs, arrange clips across video and audio tracks, add text or graphic elements, analyze media, generate captions or voiceover, validate a timeline, inspect preview frames, and export finished video with presets. The repository describes 44 tools organized around these capabilities.

This fits the Multimedia Process category for applications that need an agent to perform repeatable, inspectable video edits rather than issue a single FFmpeg command.

How it works

The agent connects to https://orccut.com/mcp using an HTTP MCP connection and an API token supplied as a Bearer authorization header. After a project is created or selected, the agent can use the editing tools to build a timeline from downloaded media. Server-side checks are performed on media supplied by URL before that media is added to a timeline.

Editing operations are validated before they are applied. A successful operation returns a new project snapshot with an incremented version and adds an entry to the project journal. The history tool can show the edits that have been made, while named versions and restore operations provide a way to return to an earlier state. The workflow documentation recommends moving from project and media setup through timeline changes, captions, validation, and export.

The mcpcut MCP server is suitable when an agent needs to make several coordinated edits, preserve an audit trail, and leave a human able to review the result in a browser.

Setup and configuration

Create an account at Orccut and generate an API token. Configure an MCP client with the hosted endpoint and send the token in the Authorization header:

{
  "mcpServers": {
    "orccut": {
      "type": "http",
      "url": "https://orccut.com/mcp",
      "headers": {
        "Authorization": "Bearer <your token>"
      }
    }
  }
}

Claude Code can be configured with its MCP command using the HTTP transport and the same Bearer token. The README specifically names Claude Code and Claude Desktop, while also stating that other clients can connect if they speak MCP.

Tools and capabilities

The documented tool groups support:

• Project creation, listing, journal inspection, annotations, named versions, and restoration.
• Multi-track video and audio timelines with clip trimming, splitting, moving, resizing, and transforms.
• Keyframes, transitions, canvas fitting, and color adjustments.
• Text overlays, image or video overlays, and cover graphics.
• Music beds, clip-level audio, and volume envelopes.
• Media download from HTTP or HTTPS URLs with server-side checking.
• Scene, audio-peak, and keyframe analysis; automatic captions; and voiceover.
• Timeline validation, preview-frame generation, and full exports with presets.

Limitations and notes

The provided material documents a hosted Orccut endpoint rather than a local MCP process. An API token and an Orccut account are required for connection. Media is supplied by HTTP or HTTPS URL, and the server checks it before timeline use. The README does not specify export formats, individual tool schemas, rate limits, or client-specific configuration beyond Claude Code and Claude Desktop.

The mcpcut MCP server does not edit projects in place: each accepted change produces another versioned snapshot and journal entry. That behavior is useful for review and recovery, but agents should account for the returned project version when chaining operations.