capcut-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet API key, obtained at https://cotlet.dev/app. Used to authenticate tool calls to the hosted Cotlet.dev CapCut server (a tool call without it answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app"). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
CapCut through Cotlet.dev. Call capcut_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capcut_guideA | How to work in CapCut (export and share drafts): its screens and the sign-in link. Call this first. |
| capcut_statusA | Check that your Cotlet.dev account and CapCut are ready: account, credits and CapCut connection. |
| capcut_openA | Open a CapCut page in your signed-in Cloud Browser (default https://www.capcut.com) to work with export and share drafts. |
| capcut_readB | Read the current CapCut page: its text and numbered buttons, links and fields. |
| capcut_clickB | Click a numbered element on the current CapCut page. |
| capcut_typeB | Type text into a numbered field on the current CapCut page. |
| capcut_closeA | Close the CapCut browser session when the work is done, so credits stop running. |
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 7 tools
The browser-action tools (open, read, click, type, close) each target a distinct step in the interaction loop, and guide vs. status are mostly separable (instructions vs. account/connection check). The only mild overlap is that both guide and status are framed as 'call first' prerequisites, which could cause a hesitation on entry.
Every tool uses the same capcut_ prefix followed by a single lowercase verb (guide, status, open, read, click, type, close). The pattern is predictable and readable throughout.
Seven tools is well-scoped for a browser-automation flow: two onboarding helpers plus the core open/read/click/type/close loop. Each tool earns its place with no redundant members.
The core loop covers opening a page, reading elements, clicking, typing and closing, but there is no scroll, wait-for-load, key press, or explicit navigate/screenshot operation. These are notable gaps for a general cloud-browser surface, though agents can partly work around them via repeated read/click.