We only use cookies to enhance your experience. No cross-site tracking, no ads. Read our Cookie Policy.
Configure Cursor so its agents can search recordings and read transcripts from your editor.
Add the configuration below to .cursor/mcp.json in a project, or to ~/.cursor/mcp.json to make Supercut available globally.
{
"mcpServers": {
"supercut": {
"type": "http",
"url": "https://mcp.supercut.ai/mcp"
}
}
}Add to .cursor/mcp.json in your project root, or configure via Cursor Settings > MCP. The first time you use the server, Cursor opens your browser to sign in to Supercut and authorize access.
Open Cursor Settings → Tools & MCPs and enable Supercut. If Cursor asks you to connect, complete the browser flow to sign in, choose your workspace, and approve access.
Confirm that Supercut has a connected status and that its tools appear in Agent chat. Cursor Agent CLI users can also list configured servers from the terminal.
cursor-agent mcp listStart with a read-only request so you can see the recording context your client receives.
Search Supercut for the recording that explains this code path and summarize the expected behavior.Need client-specific troubleshooting? Read the Cursor MCP guide.
How Supercut MCP gives agents permission-aware access to recordings, transcripts, and frames.
Add the Supercut MCP server in Claude Code, then sign in only if Claude asks you to.
Connect Supercut as a remote connector in Claude Desktop and authorize access in the browser.
Point Codex at Supercut’s MCP endpoint and bring recording context into your coding sessions.
Add Supercut to VS Code for Copilot-powered workflows over your recordings.