Connect OpusClip AI Producer MCP

Production. MCP endpoint: https://producer.opus.pro/api/mcp. 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.
• Use a client with remote HTTP MCP support. Codex and Claude Code use terminal commands; Cursor Desktop uses its MCP configuration and authentication UI.
• Inspect the existing installation first. Keep a working installation on this environment. Preserve unrelated plugins, servers, and configuration.
• Use this page's endpoint. 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.
• Installation ends after verification. Do not request a video, upload files, create a project, edit, or render as an installation test.
• 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.

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 mcp get ai-producer

3. 3

   If the server is absent, register this endpoint. If the full plugin already supplies it, keep that connection rather than adding a duplicate server.

   Add MCP server

   codex mcp add ai-producer --url https://producer.opus.pro/api/mcp

   The add command can start OAuth and wait for browser sign-in. Complete that flow and let the command return. Use the login command below if authentication did not finish.

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 mcp get ai-producer

   Verify from the command line only. 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 server 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. Start a new task and call it there, before anything else. get_pricing with {} returns a structured response without uploading media, creating a project, or spending credits.

   Report the client, target environment, 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.

[mcp_servers.ai-producer]
url = "https://producer.opus.pro/api/mcp"
oauth_resource = "https://producer.opus.pro/api/mcp"

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 mcp get ai-producer

2. 2

   If the server is absent, register this endpoint. If the full plugin already supplies it, keep that connection rather than adding a duplicate server.

   Add MCP server

   claude mcp add --scope user --transport http ai-producer https://producer.opus.pro/api/mcp

3. 3

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

   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 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 ai-producer

   A connected status confirms the server connection; a configuration listing alone does not. Start a new session if the installed tools 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, 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.

{
  "mcpServers": {
    "ai-producer": {
      "type": "http",
      "url": "https://producer.opus.pro/api/mcp"
    }
  }
}

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. 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

   Choose user scope at ~/.cursor/mcp.json or project scope at .cursor/mcp.json. Inspect the existing configuration and Customize > MCPs first. If the plugin already provides the working ai-producer connection, keep it and do not add a duplicate.

2. 2

   Merge only the ai-producer entry below into the chosen file's existing mcpServers object. Create the file only if it does not exist. Never replace the whole file or remove other servers or settings. This connection provides tools without the plugin's editing skills.

   Cursor MCP configuration

   {
     "mcpServers": {
       "ai-producer": {
         "url": "https://producer.opus.pro/api/mcp"
       }
     }
   }

3. 3

   User action: run Developer: Reload Window from the Command Palette, then open Customize. 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.

For the complete editing workflow, install the plugin. It includes these MCP tools and the editing skills.