为 AI Agent 安装 StarCut

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
Marketplace: starrank-soft/starcut-plugin
Package: claude-code
MCP server: https://api.starcut.io/mcp

Host gate

Run installation only from Claude Code on the machine where StarCut will be used. A browser-only Claude chat cannot install the desktop Claude Code plugin or MCP configuration.

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

Read starcut.io/claude.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.

Use the Claude Code CLI available in this local session (claude). Do not substitute another Claude binary from an unrelated install path unless the user explicitly confirms it is the same Claude Code app.

claude --version
claude mcp login --help

The login flow requires Claude Code with claude mcp login support. If the CLI is missing or too old, upgrade with claude update before continuing.

Before installing, verify Node.js is available:

node --version

Use the bundled helper for login and configuration. Do not recreate its flow with inline shell, Python, or curl, and never paste credentials into the conversation.

Install

If this machine may have used StarCut before, check for a legacy standalone MCP server:

claude mcp get starcut

If that command finds a server named exactly starcut, remove the legacy standalone entry before installing the plugin:

claude mcp remove starcut

Add the marketplace for this environment:

claude plugin marketplace add starrank-soft/starcut-plugin

Inspect available marketplaces, then install StarCut from the marketplace that contains it. Prefer the qualified form when multiple marketplaces exist:

claude plugin marketplace list
claude plugin install starcut@starcut

If install reports that reload is required:

# Inside the Claude Code session
/reload-plugins

Log in

Inspect MCP health before starting OAuth:

claude mcp list
claude mcp get starcut

Only when StarCut needs authentication, run one login and wait for it to finish. Prefer the plugin login script when the shell is non-interactive:

sh "<STARCUT_PLUGIN_REPO>/claude-code/scripts/login-starcut.sh" > /tmp/starcut-login.log 2>&1 &

Poll /tmp/starcut-login.log until Claude opens the StarCut authorization page or prints Authenticated. If the script is unavailable, run:

claude mcp login plugin:starcut:starcut

If that name is rejected, retry with the exact server name from claude mcp list. Never start a second login while another login is still active. Complete the browser OAuth flow, then start a new Claude Code session so StarCut tools load.

Verify

claude plugin list
claude mcp list
claude mcp get plugin:starcut:starcut

Success criteria:

1. starcut appears in claude plugin list as installed and enabled.
2. The StarCut MCP server is authenticated and its tools load successfully.
3. The MCP endpoint in use is:

https://api.starcut.io/mcp

Start a new Claude Code session before calling StarCut tools.

Failure-mode debugging

Treat half-installed or installed-but-not-authenticated states as failures. Recover the matching symptom and resume at the interrupted step.

• claude missing: install or repair the Claude Code CLI before retrying login.
• claude mcp login missing: upgrade Claude Code with claude update.
• Login says stdin is not a terminal: use the plugin login script above or a PTY wrapper instead of invoking claude mcp login directly in a non-interactive shell.
• A legacy standalone starcut MCP server conflicts with the plugin: remove only the standalone entry with claude mcp remove starcut.
• Login timeout or OAuth 5xx before authentication succeeds: wait for the current login process to exit, retry once with backoff, then rerun login. Do not run concurrent login attempts.
• Connected before OAuth succeeds is not enough. Wait for the authenticated login output, then start a new session.

If the endpoint, plugin, or authentication state is wrong, fix that exact step and verify again. Starting a new conversation does not repair installation or login.

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.