Skip to main content
Glama
README.md
# How to connect CapCut to ChatGPT, Claude and any AI agent

**Yes, ChatGPT, Claude and other AI agents can work in your CapCut account.** Cotlet lets your agent export drafts, add auto captions, send review links and manage team spaces in your own CapCut account.

## What you can ask

> Export my Launch teaser draft as a 1080p MP4.

> Add auto captions to the latest draft and send me a review link.

> List the editors in my Default space.

> Search the template gallery for a summer product launch.

> Invite Maya Brooks to our team space as an editor.

## Connect in 2 minutes

Get your API key at https://cotlet.dev/app and export it as `COTLET_API_KEY`.

### Claude Code

```bash
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"
```

### ChatGPT

Settings → Apps → add connector URL `https://cotlet.dev/mcp/v1`, then sign in with Cotlet.dev. No API key needed.

### Cursor

Copy `.cursor/mcp.json` from this repo into your project:

```json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

## Run it locally (stdio)

This repo is a real MCP server. It speaks MCP over stdio, lists its CapCut tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.

```json
{"mcpServers":{"capcut":{"command":"uvx","args":["capcut-mcp"],"env":{"COTLET_API_KEY":"your-key"}}}}
```

Or with Docker:

```bash
docker build -t capcut-mcp .
docker run -i --rm -e COTLET_API_KEY capcut-mcp
```

Tools: `capcut_guide`, `capcut_status`, `capcut_open`, `capcut_read`, `capcut_click`, `capcut_type`, `capcut_close`. Without `COTLET_API_KEY` a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".

## Command line

Python 3.10+, nothing else to install. From PyPI:

```bash
pip install capcut-mcp        # or run it once: uvx capcut-mcp connect
capcut-mcp connect
```

Or straight from this repo:

```bash
export COTLET_API_KEY="your-key"
python3 capcut_agent.py connect   # ready config for Claude Code, Cursor, ChatGPT
python3 capcut_agent.py status    # is CapCut ready in your Cotlet.dev account
python3 capcut_agent.py guide     # CapCut screens and sign-in link
python3 capcut_agent.py read      # open CapCut, read the page, close the browser
python3 capcut_agent.py tools     # list Cotlet.dev tools
python3 capcut_agent.py serve     # start the stdio MCP server (same as no argument)
```

## Questions from CapCut users

**Does CapCut have an MCP server or an API?**

CapCut has no public API for drafts, exports or sharing and publishes no MCP address for Claude or Cursor. Cotlet runs hosted CapCut tools over MCP and REST.

**How do I connect CapCut to ChatGPT?**

Sign in to CapCut in your Cotlet Cloud Browser, enable CapCut for agents, then add https://cotlet.dev/mcp/v1/connect in ChatGPT.

**Can I use CapCut with Claude?**

Yes. Add https://cotlet.dev/mcp/v1 as a custom connector in Claude after enabling CapCut for agents.

**What can an AI agent do in CapCut?**

Your agent can export drafts, add auto captions, share drafts for review, manage team spaces and search the template gallery.

## Find it on

- [CapCut on Cotlet.dev](https://cotlet.dev/integrations/capcut-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=capcut&utm_content=find)
- [PyPI package capcut-mcp](https://pypi.org/project/capcut-mcp/)
- [Odel](https://odel.app/modules/cotlet/capcut)
- [mcpbeat](https://mcpbeat.com/mcp-servers/cotlet/capcut/)
- [Step-by-step guide (PDF) on Internet Archive](https://archive.org/details/cotlet-connect-capcut-to-ai-agents-guide)

## Also works with


- [All apps connected through Cotlet.dev](https://github.com/cotlet-connect)

---

More: https://cotlet.dev/integrations/capcut-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=capcut

Start free: https://cotlet.dev/signup?app=capcut&utm_source=github&utm_medium=readme&utm_campaign=capcut

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness3/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues