capcut-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAPCUT_DRAFT_ROOT | No | Override the draft root path if CapCut lives somewhere else. |
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 has a clearly distinct purpose: listing projects, reading a timeline, listing referenced media, creating a basic project, detecting beats, and creating a beat-synced project. The two create tools are differentiated by their specific behaviors and the beat edit tool explicitly builds on beat detection. No two tools could be reasonably confused for the same operation.
All tools use a consistent capcut_ prefix and snake_case, and five of six follow a verb_noun pattern (list_projects, read_project, create_project, detect_beats, create_beat_edit). The outlier is capcut_project_media, which is noun-first rather than verb-first, a minor deviation that doesn't harm readability.
Six tools is well-scoped for a local CapCut project manipulation server, covering inspection, media validation, creation, and beat-based creation without redundancy. Each tool earns its place and there are no unnecessary additions.
The surface covers listing, reading, media checking, and creating new projects, but lacks update, delete, rename, or any modification of existing projects. This is a notable gap for a project management domain, though the creation tools explicitly avoid modifying existing projects by design.