capcut-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAPCUT_DRAFT_ROOT | No | Override the default CapCut draft root directory. Defaults to %LOCALAPPDATA%\CapCut\User Data\Projects\com.lveditor.draft on Windows and ~/Movies/CapCut/User Data/Projects/com.lveditor.draft on macOS. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capcut_list_projectsA | List the CapCut projects in the local draft library, newest first, with duration, resolution and track count. Start here — every other tool takes a project name from this list. |
| capcut_read_projectA | Read one project's timeline: every track, and every segment on it with its start time, duration, speed and the material it plays. Times are in seconds. |
| capcut_project_mediaA | List the source files a project references, with size, and whether each still exists on disk. Use this to find edits broken by moved or deleted media. |
| capcut_create_projectA | Build a new CapCut project from video files, laid end to end on one track, each optionally trimmed. Creates a new project only — it never modifies an existing one, and refuses if a project of that name is already there. CapCut must be closed. Open the result in CapCut to confirm it loads. |
| capcut_detect_beatsA | Find the tempo and beat times of any file with audio. Returns BPM, the spacing between beats, and every beat in seconds. Useful on its own for deciding how long cuts should be. |
| capcut_create_beat_editA | Build a new project whose cuts land on the beat. Cut lengths come from the detected tempo; the footage for each cut is sampled evenly across the source, so a short edit surveys the whole video rather than its opening. Same safety rules as capcut_create_project. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct operation: detecting beats, creating beat-synced edits, creating general projects, listing/reading projects, and checking media files. Even the two creation tools are clearly differentiated by their specialized vs. general purpose.
Most tools follow a consistent 'capcut_<verb>_<noun>' pattern (detect_beats, create_project, list_projects, read_project). The exception is 'capcut_project_media', which uses a noun phrase rather than a verb-action form, making it a minor deviation in an otherwise consistent naming scheme.
With 6 tools, the server is tightly scoped for its purpose: analyzing audio, creating projects, and inspecting existing drafts. This is a reasonable size that covers the core workflows without unnecessary bloat.
The set covers project creation (general and beat-based), listing, reading timelines, and checking media integrity. Notable gaps include lack of project deletion, modification, or export/render, but these may be outside the server's intended scope, so the current surface is mostly complete for its niche.