Skip to main content

StarCut agent plugin

Install StarCut for AI agents

Copy the install prompt for Cursor, then follow the guide below to complete setup.

Install prompt

Read starcut.io/cursor.md and install StarCut for me. Complete authentication and verification.

Paste this prompt into a Cursor Agent conversation.

Install guide

Install StarCut

Reply to the user in the language they are currently using. The instructions below are written only in English so there is one execution contract.

This guide is generated for the current environment:

Mode: production
Marketplace: https://github.com/starrank-soft/starcut-plugin.git
Package: https://github.com/starrank-soft/starcut-plugin/tree/main/cursor
MCP server: https://api.starcut.io/mcp

Host gate

Run installation only from Cursor Agent on the machine where StarCut will be used. A Cursor web session or remote-only workspace that cannot write local plugin directories is not enough.

If this is not the correct host surface, stop and ask the user to open that host and send:

Read starcut.io/cursor.md and install StarCut for me. Complete authentication and verification.

Execution contract

Read this whole guide before running commands. Complete installation, login, and verification in order. Do not stop after an intermediate success. Do not claim later steps passed when an earlier step failed.

Cursor does not yet expose a ChatGPT-style marketplace CLI for StarCut. Install by materializing the local plugin package and wiring MCP, then complete OAuth in Cursor Settings. Prefer shell commands over vague "copy the folder" instructions.

If the starrank-soft/starcut-plugin repository is not already cloned locally, clone it first, then use its cursor/ directory as SOURCE:

git clone https://github.com/starrank-soft/starcut-plugin.git
SOURCE="$(pwd)/starcut-plugin/cursor"

Install

Resolve the Cursor config home and install destination:

  • macOS/Linux: CURSOR_HOME="$HOME/.cursor"
  • Windows PowerShell: $CURSOR_HOME = Join-Path $env:USERPROFILE ".cursor"

Create the local plugin directory and sync the package files.

macOS/Linux:

SOURCE="<STARCUT_PLUGIN_REPO>/cursor"
CURSOR_HOME="$HOME/.cursor"
DEST="$CURSOR_HOME/plugins/local/starcut"
mkdir -p "$DEST"
rsync -a --delete "$SOURCE"/ "$DEST"/

Windows PowerShell:

$Source = "<STARCUT_PLUGIN_REPO>\cursor"
$Dest = Join-Path $env:USERPROFILE ".cursor\plugins\local\starcut"
New-Item -ItemType Directory -Force -Path $Dest | Out-Null
robocopy $Source $Dest /MIR /NFL /NDL /NJH /NJS /nc /ns /np
if ($LASTEXITCODE -ge 8) { throw "robocopy failed: $LASTEXITCODE" }

Also ensure the user MCP config contains the StarCut HTTP server so OAuth can attach even if the local plugin surface is slow to refresh. Merge this entry into ~/.cursor/mcp.json (create the file if missing) without deleting other servers:

{
  "mcpServers": {
    "starcut": {
      "type": "http",
      "url": "https://api.starcut.io/mcp"
    }
  }
}

Do not add oauth_resource. Cursor discovers OAuth from the remote URL. Reload the Cursor window after the files are written.

Log in

Open Cursor Settings β†’ Tools & MCP. Find starcut. If it shows Needs authentication / Connect, complete the browser OAuth flow once and wait for it to finish. Never start a second Connect while one is still active. Start a new Agent conversation afterwards.

Verify

Confirm all of the following before opening a project:

test -f "$HOME/.cursor/plugins/local/starcut/.cursor-plugin/plugin.json"
test -f "$HOME/.cursor/plugins/local/starcut/mcp.json"
test -f "$HOME/.cursor/plugins/local/starcut/skills/basics/SKILL.md"

Windows PowerShell equivalents:

Test-Path "$env:USERPROFILE\.cursor\plugins\local\starcut\.cursor-plugin\plugin.json"
Test-Path "$env:USERPROFILE\.cursor\plugins\local\starcut\mcp.json"
Test-Path "$env:USERPROFILE\.cursor\plugins\local\starcut\skills\basics\SKILL.md"

Also confirm both MCP configs point at:

https://api.starcut.io/mcp
grep -R "https://api.starcut.io/mcp" "$HOME/.cursor/plugins/local/starcut/mcp.json" "$HOME/.cursor/mcp.json"

In the new Agent conversation, confirm the StarCut project tools are available. If the endpoint, plugin files, or authentication state is wrong, fix that exact step and verify again. Starting a new conversation does not repair a missing local plugin directory or a wrong MCP URL.

Start editing

After installation succeeds, tell the user to start a fresh conversation and send the prompt below in their language. Do not add implementation details.

StarCut is ready. Help me start a new video project. Briefly tell me how you can
help bring it to life, then ask what materials I have and what I want the finished
video to be like.

Completion

Report success only after all of these are true:

  1. The plugin or project bundle is installed and enabled.
  2. starcut is authenticated against https://api.starcut.io/mcp.
  3. The user received the short startup prompt for a fresh conversation.

If any step fails, report the exact failed step and error without claiming later steps passed.