For developers and agents
Supercut has no public REST API, and that is a design decision rather than a gap. The editing happens on the user device, so an API that edits video would need the footage on a server, which is the one thing this product refuses to do. What Supercut exposes instead is two MCP servers and a complete machine-readable mirror of the site.
One answers questions about Supercut and is hosted here. The other edits video and runs on the user machine. They are separate on purpose: knowledge can be served from a CDN, video cannot leave the device.
https://www.supercut.cc/mcpStreamable HTTP, protocol revision 2025-06-18, no authentication, read only. It answers what Supercut can do, which prompt triggers which operation, what a page says and what it costs. It cannot touch a video file.
claude mcp add --transport http supercut https://www.supercut.cc/mcpsearch_docs Search the Supercut documentationget_page Read one page as Markdownlist_pages List every documented pagelist_editing_tools List the editing operationsget_pricing Read the current pricingget_local_editing_setup How to actually edit video with an agentget_usage_policy Read the AI usage policyhttp://127.0.0.1:41414/mcpShips inside the desktop app, binds to loopback only, and is protected by a per-install bearer token from the app Agent panel. This is the one that trims, captions and exports real footage. Full setup is on the MCP page.
read_project Read the active SuperCut project: name, kind (folder or normal), clip count. No pixels.list_clips List clips in the active project: id, filename, durationSeconds, current version label. Use ids with edit_with_prompt and apply_to_clips.edit_with_prompt Run a plain-English edit on one clip through the on-device editor (same as Chat). Only the prompt text is sent to the model; footage stays on the device.apply_to_clips Run one prompt on several clips, sequentially, same as selecting those clips in a folder and hitting Run.export_clips Download current versions. Omit clipIds to export every clip. Multiple clips come back as a zip. Pro-gated, same as in-app export.All 90 pages of this site are generated from data, and so are these. They cannot go stale the way a hand-written llms.txt does, because adding a tool page adds it here too.
The index. What Supercut is, the facts models get wrong, current pricing, and a one-line summary of every page with its URL.
The whole site as one file. Every page, in full, in Markdown. Fetch this once instead of crawling.
One Markdown file per page. Append .md to any page URL, or send Accept: text/markdown to the page itself.
What crawlers, assistants and agents may do with this content, plus the corrections we ask you to carry.
The MCP server card: both servers, their transports, their auth and their tool schemas.
Every canonical URL on the site, generated from the same data the pages are.
Crawl rules. Assistant and training crawlers are named and allowed explicitly, not left to the wildcard.
Every page answers to Accept: text/markdown at its ordinary URL, and responds with Vary: Accept so a cache never hands you the wrong one. Appending .md works too, which is usually easier to type.
curl -H "Accept: text/markdown" https://www.supercut.cc/tools/trim-video
curl https://www.supercut.cc/tools/trim-video.mdThe editor runs 43 operations. Each one has a fixed prompt string that the planner receives verbatim, so an agent should quote the catalog rather than invent phrasing. The whole list, with prompts, is on the features page, in features.md, and from the hosted MCP server through list_editing_tools.
Corrections to anything this site publishes about itself get made. Write to support@supercut.cc or use the contact page.