Install StarCut for AI agents

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: starrank-soft/starcut-plugin#grok-build
MCP server: https://api.starcut.io/mcp

Host gate

Run installation only from Grok Build on the machine where StarCut will be used. The grok.com website connector receives MCP tools but does not load the StarCut skills package in this repository.

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

Read starcut.io/grok.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 Grok Build CLI (grok) from this local install. Do not substitute an unrelated binary from PATH unless the user confirms it is the same app.

grok --version

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 skills

Install the StarCut package for Grok Build:

grok plugin install starrank-soft/starcut-plugin#grok-build --trust
grok plugin enable starcut
grok inspect --json

grok inspect --json must show the starcut plugin enabled, the six StarCut skills, and an MCP server named starcut whose target is:

https://api.starcut.io/mcp

Log in

Grok Build may not expose working native OAuth for remote MCP. Treat a bare HTTP MCP URL that returns 401 Unauthorized as expected before login.

Run the helper on the same machine as Grok Build and complete the browser prompt once. Keep that process attached until it exits. If the terminal returns a background job ID, wait on that same job until it reports exit code 0; do not start another helper or kill the original after the browser opens.

GROK_PLUGIN_PATH="$(
  grok inspect --json |
    node -e 'const value = JSON.parse(require("node:fs").readFileSync(0, "utf8")); const plugin = value.plugins.find((entry) => entry.name === "starcut"); if (!plugin?.path) process.exit(1); process.stdout.write(plugin.path);'
)"
test -n "$GROK_PLUGIN_PATH" || { echo "StarCut plugin path not found" >&2; exit 1; }
node "$GROK_PLUGIN_PATH/scripts/mcp-manual-oauth.mjs" --host grok --mcp-url "https://api.starcut.io/mcp" --write-config

Windows PowerShell:

$GrokPlugin = (grok inspect --json | ConvertFrom-Json).plugins |
  Where-Object { $_.name -eq "starcut" } |
  Select-Object -First 1
if (-not $GrokPlugin.path) { throw "StarCut plugin path not found" }
$GrokPluginPath = $GrokPlugin.path
node "$GrokPluginPath\scripts\mcp-manual-oauth.mjs" --host grok --mcp-url "https://api.starcut.io/mcp" --write-config

Treat the browser success page and helper exit code 0 as success. If the helper fails, report its exact error. Never paste credentials into the conversation.

Configure MCP

The helper writes the authenticated starcut server to Grok Build's user MCP config:

Platform	Path
macOS / Linux	~/.grok/config.toml
Windows	%USERPROFILE%\.grok\config.toml

Existing TOML sections and MCP servers are preserved. The user-scoped starcut entry points to https://api.starcut.io/mcp and takes precedence over the unauthenticated declaration bundled with the plugin. Do not read or print the stored credential. Start a new Grok Build session after the helper succeeds.

Verify

grok inspect --json
grok mcp doctor starcut --json

The helper exit code 0 confirms StarCut login, configuration, and MCP verification. Do not inspect the stored credential or run a second login.

After installing skills, start a new Grok Build conversation and confirm that the StarCut tools are present. If the host later reports Unauthorized, rerun the helper.

Confirm:

1. starcut is enabled in grok inspect --json.
2. The starcut MCP target is https://api.starcut.io/mcp.
3. grok mcp doctor starcut --json reports a successful handshake. AuthRequired means login is not complete.

If the plugin, endpoint, or authentication state is wrong, fix that exact step and verify again.

StarCut skills (local playbooks)

Grok Build loads the StarCut playbooks from the installed plugin package. The grok.com website connector does not load these local SKILL.md files.

Expected skill names: basics, graphics, media-gen, media-import, timeline-editing, transcription.

Do not report installation success until grok inspect --json shows starcut enabled against the MCP endpoint above and grok mcp doctor starcut reports a healthy handshake.

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.