Install OpusClip AI Producer Plugin

Production. MCP endpoint: https://producer.opus.pro/api/mcp. Marketplace: ai-producer-plugins, ref main. Plugin: aip. MCP server name: ai-producer.

• Use only the section for your current client. Codex is the primary supported client; Claude Code and Cursor Desktop are also supported. Do not install into other clients just because they are available.
• Plugin installation requires a local client with shell access, Git, and plugin support. Cursor uses a complete local plugin copy. If the current client cannot install plugins, report that limitation; do not silently substitute an MCP-only connection.
• Inspect the existing installation first. Keep a working installation on this environment. Preserve unrelated plugins, servers, and configuration.
• Use this page's endpoint and marketplace ref. Other environments install under different names and are left alone. If an installation under the names above targets another environment, follow the recovery instructions below.
• For Codex and Claude Code, run each client command through the executable that client actually ships. The Codex section resolves its bundled CLI first. Cursor Desktop follows its own copy, reload, and Customize steps below.
• Let the user complete browser sign-in with their OpusClip account. Never ask them to paste passwords, cookies, or access tokens into the conversation. Each host's sign-in step below owns how its browser is opened; follow that step rather than opening the authorization URL yourself, and wait for sign-in to finish.
• This installation task ends after verification and the editing handoff in the final step. Do not request a video, upload files, create a project, edit, or render inside it; that work belongs to the separate editing task the handoff creates.
• Follow your client's verification step. The Codex installer verifies from its command line; Claude Code verifies in a fresh session; Cursor reloads its window and verifies in a fresh Agent conversation.
• Follow the editing handoff for your client after verification. Keep editing in a separate conversation, and report whether it was opened or the user still needs to open it.

/goal Read https://producer.opus.pro/docs/plugins, follow it exactly to install AI Producer plugin, then create a new task for me

The leading /goal is a Codex command. From a Claude Code or Cursor Desktop conversation, send the same message without it; follow that client's own editing handoff below.

1. 1

   Resolve the codex executable before running anything else. The Codex desktop app bundles its own, at /Applications/ChatGPT.app/Contents/Resources/codex on macOS; on Windows or Linux, locate the bundled executable inside the installed app the same way. Use that binary for every command on this page. A bare codex on PATH is the fallback for a separately installed CLI, never the default: a desktop-only installation has no PATH entry at all, and the commands below fail as missing rather than as unsupported.

   Resolve the Codex executable

   /Applications/ChatGPT.app/Contents/Resources/codex --version || codex --version

2. 2

   Inspect the current configuration. A missing AI Producer entry means installation is needed; a command that is unavailable means the client must be updated or a supported installation surface used.

   Inspect installation

   codex plugin list
   codex mcp get ai-producer

3. 3

   If the plugin is absent, add the marketplace and install it. If the marketplace already exists, check its source and ref before reusing it.

   Install plugin

   codex plugin marketplace add https://github.com/opus-pro/ai-producer-plugin.git --ref main
   codex plugin add aip@ai-producer-plugins

4. 4

   Sign in if this connection is not already authenticated, and let the user complete browser sign-in.

   Run the check below, then exactly one of the two sign-in commands. On macOS inside a Codex Desktop task, a successful check means the combined command can bring this installer task back to the front after login. Otherwise, use the plain login command and return to this task manually.

   Check for automatic return

   test -n "$CODEX_THREAD_ID"

   Sign in and return to this task on macOS

   codex mcp login ai-producer && open -b com.openai.codex "codex://threads/$CODEX_THREAD_ID"

   Sign in without automatic return

   codex mcp login ai-producer

   The login command opens the browser itself and blocks until sign-in completes. When a browser window opened, do not also open the authorization URL the command prints: the callback is one-shot, so the second window lands on a refused connection after the first one has already consumed it. Open that printed URL once, while the command is still running, only if no browser opened at all, as in a headless or opener-restricted session. Wait for the command to print Successfully logged in to MCP server. Only when the command exits without that line, ask the user the question below and continue once they confirm. Never ask for a password, cookie, or access token instead. If the open suffix fails after the CLI prints its success line, sign-in still succeeded; do not run the login command again.

   Sign-in acknowledgement

   Please sign into the OpusClip account to continue, let me know when it's done

5. 5

   Check that the effective server URL is https://producer.opus.pro/api/mcp.

   Inspect target endpoint

   codex plugin list
   codex mcp get ai-producer

   Verify from the command line only. codex plugin list must list the plugin as installed and enabled, and codex mcp get ai-producer must report https://producer.opus.pro/api/mcp. enabled: true confirms configuration only. It does not prove successful authentication.

   This installer thread never sees the tools of a plugin it just installed, so get_pricing cannot be called here and its absence is not a failed installation. Do not open a session, retry, or reinstall to reach it. The authenticated read is proved by the editing task's own first tool call; that task needs no instruction to make it. get_pricing with {} returns a structured response without uploading media, creating a project, or spending credits.

   Report the client, target environment, plugin installation, authentication, and tool verification separately. The tool check is reported as the next task's first action, never as something done here. If a new session or sign-in is still needed, name that pending step instead of claiming the installation is ready.

6. 6

   Only after the plugin is installed and sign-in is complete, create a separate task the user can see, with exactly this initial prompt. This installation task itself never uploads a video, edits, renders, or creates an AI Producer project.

   Editing task prompt

   [@AI Producer](plugin://aip@ai-producer-plugins) I'd like to edit a video with AI Producer. Briefly explain how you can help, then ask me to upload my footage before we start.

   Call create_thread with one of these argument shapes. Prefer the projectless one, because the work edits a video rather than a repository. Use the project-scoped shape only when this installer thread itself belongs to a project, and keep projectId inside target exactly as shown.

   Create the editing task

   {
     "prompt": "<the editing task prompt above, verbatim>",
     "target": { "type": "projectless", "directoryName": "ai-producer-edit" },
     "title": "Edit my video with AI Producer"
   }

   Create the editing task inside a project

   {
     "prompt": "<the editing task prompt above, verbatim>",
     "title": "Edit my video with AI Producer",
     "target": { "type": "project", "projectId": "<the installer thread's project id>", "environment": { "type": "local" } }
   }

   That prompt is the only message this installer sends to the new task. Never call send_message_to_thread or otherwise append instructions to it.

   Then call navigate_to_codex_page with the returned threadId. This is required: without it the new task exists but never comes to the front, and the user is left in the installer. If that tool is not callable here, run the deep link instead.

   Open the new task

   open "codex://threads/<threadId>"

   Then close this thread with exactly this line, naming the task you created.

   Installer self-report

   Installed and signed in. I created your editing task "Edit my video with AI Producer" (<threadId>) and opened it -- continue there. This thread was only the installer.

   If this client exposes neither task creation nor the deep link, report that limitation and direct the user to the Start editing button at https://producer.opus.pro/plugin, which starts the same prompt.

codex plugin marketplace upgrade ai-producer-plugins

1. 1

   Inspect the current configuration. A missing AI Producer entry means installation is needed; a command that is unavailable means the client must be updated or a supported installation surface used.

   Inspect installation

   claude plugin list
   claude mcp get plugin:aip:ai-producer

2. 2

   If the plugin is absent, add the marketplace and install it. If the marketplace already exists, check its source and ref before reusing it.

   Install plugin

   claude plugin marketplace add https://github.com/opus-pro/ai-producer-plugin.git#main
   claude plugin install aip@ai-producer-plugins --scope user

3. 3

   Start a new session so the plugin server is discovered, then sign in. If a fresh session is required to continue, report installation complete and authentication pending.

   Sign in

   /mcp

   Open the authorization URL in this client's internal browser when it exposes one; otherwise let the default sign-in browser flow run. Wait for sign-in to finish before verifying. Only when this client gives no sign-in completion signal, ask the user the question below and continue once they confirm. Never ask for a password, cookie, or access token instead.

   Sign-in acknowledgement

   Please sign into the OpusClip account to continue, let me know when it's done

   Inside a session, /mcp, select the plugin:aip:ai-producer server, then authenticate. If an authenticate tool is exposed for that server, it can start the same browser flow.

4. 4

   Check that the effective server URL is https://producer.opus.pro/api/mcp.

   Inspect target endpoint

   claude mcp get plugin:aip:ai-producer

   A connected status confirms the server connection; a configuration listing alone does not. Start a new session if the installed tools or skills are not loaded.

   In the loaded session, verify that the AI Producer tools are available and call get_pricing with {}. A successful structured response verifies an authenticated read without uploading media, creating a project, or spending credits.

   Report the client, target environment, plugin installation, authentication, and tool verification separately. If a new session or sign-in is still needed, name that pending step instead of claiming the installation is ready.

5. 5

   Only after the plugin is installed, sign-in is complete, and get_pricing returned, hand the user this exact prompt as the first message of a fresh session, started in a directory with no repository: the work edits a video, not code. This installation session itself never uploads a video, edits, renders, or creates an AI Producer project.

   Editing task prompt

   /aip:aip I'd like to edit a video with AI Producer. Briefly explain how you can help, then ask me to upload my footage before we start.

   Report the handoff as pending until the user starts that session; do not direct them to another client.

claude plugin marketplace update ai-producer-plugins
claude plugin update aip@ai-producer-plugins

Use Cursor Desktop Agent with local filesystem and terminal access. Cursor Web and Cloud Agents are outside this installation path. Your organization may restrict local plugins or MCP servers.

Installing agent: complete the file steps, then give the user the reload, sign-in, and fresh-conversation steps below in one message before they reload. Include the editing prompt in that same message. Report the files installed or configured, with sign-in and tool verification pending until observed. The user completes Cursor's interface actions; do not wait for this installing conversation to load new tools.

1. 1

   Inspect Customize and ~/.cursor/plugins/local/aip first. Keep an existing working production installation. A marketplace plugin with the same name takes precedence over a local copy; resolve that conflict before continuing. Preserve unrelated plugins and MCP entries.

   Use the public repository's main branch. If you already have its checkout, update that checkout; otherwise clone it into an unused directory:

   Cursor plugin source

   git clone --branch main --single-branch https://github.com/opus-pro/ai-producer-plugin.git ai-producer-plugin && cd ai-producer-plugin

2. 2

   From the repository root, confirm this revision contains plugins/aip/.cursor-plugin/plugin.json, then copy the complete plugins/aip directory, including dotfiles. The command below stops if the destination already exists. Do not replace an unrelated directory or use an external-directory symlink: Cursor skips those symlinks. If the manifest is missing, stop and obtain a revision containing Cursor support; do not silently switch to MCP-only setup.

   Copy Cursor plugin

   if test ! -f plugins/aip/.cursor-plugin/plugin.json || test -L plugins/aip; then
     echo "Use a checkout containing the Cursor plugin package."
     exit 1
   elif test -L "$HOME/.cursor" || test -L "$HOME/.cursor/plugins" || test -L "$HOME/.cursor/plugins/local"; then
     echo "The local plugin path has a symlinked parent. Inspect it before continuing."
     exit 1
   elif test -e "$HOME/.cursor/plugins/local/aip" || test -L "$HOME/.cursor/plugins/local/aip"; then
     echo "The local aip path already exists. Inspect its ownership before updating."
     exit 1
   else
     mkdir -p "$HOME/.cursor/plugins/local" &&
       cp -R plugins/aip "$HOME/.cursor/plugins/local/aip"
   fi

3. 3

   User action: run Developer: Reload Window from the Command Palette, then open Customize. Confirm the plugin exposes aip, aip-composition, aip-dynamic-caption, aip-framing, and aip-setup. Under MCPs, select ai-producer and choose Authenticate. Complete the browser sign-in with your OpusClip account, then return to Cursor. Use the same action if sign-in expires.

4. 4

   User action: open a fresh Agent conversation after reload and sign-in. Its first check is get_pricing with {}. This free, read-only check verifies the authenticated connection. Report the actual result; a configured server alone does not prove sign-in. Do not upload media, create a project, or export as an installation test.

   Paste the prompt below into that fresh conversation. It verifies the connection before starting the editing handoff. The installer gives you this prompt before reload, even when it cannot open another conversation or observe sign-in. Until you open it, the handoff remains pending.

   Cursor editing prompt

   First verify the AI Producer connection with get_pricing({}). If it succeeds, use the aip skill to help me edit a video and ask which video to use. Do not upload media or create a project as a connection test. If sign-in or tools are unavailable, report that pending step.

   During editing, open project links in your browser. For a follow-up change, use the project's copy as reference action and paste that reference back into Cursor with the requested change.

The plugin includes both skills and MCP. Use MCP-only setup when you intentionally need the tools without the bundled editing skills.