> ## Documentation Index
> Fetch the complete documentation index at: https://help.opus.pro/llms.txt
> Use this file to discover all available pages before exploring further.

# Setup OpusClip in your agent

Connect OpusClip to an AI agent and call the API from natural-language prompts such as "clip this video" or "schedule this clip to post tomorrow at 9am."

Pro-tier API access is in **Beta**. The limits described on [Limitations](/api-reference/limitation) apply to **Pro Beta** and **Max** unless noted otherwise. Business customers have API access per their contract.

OpusClip provides two integrations: **MCP** and **Skill**. You can use either, or both.

<Steps>
  <Step title="Install">
    ### MCP

    Endpoint:

    ```
    https://api.opus.pro/api/mcp
    ```

    Any OpusClip account can complete the OAuth flow and view the tool catalog. Calling a tool requires **Pro Beta**, **Max**, or **Business** plan access; without it, the host returns an upgrade prompt.

    **Claude.ai — from the connector directory** *(coming soon)*

    Once OpusClip is listed in the Claude.ai connector directory, open **Settings → Connectors**, find **OpusClip**, click **Add**, and complete the OAuth sign-in.

    <Note>
      Directory listing is in progress. Until it is live, use the custom-connector steps below. The endpoint and behaviour are identical.
    </Note>

    **Claude.ai — as a custom connector**

    * Open **[claude.ai/customize/connectors](https://claude.ai/customize/connectors)** and click **Add custom connector**.
    * Paste the endpoint above, name the connector `OpusClip`, and click **Connect**.
    * Sign in with your OpusClip account in the OAuth window.
    * Start a new conversation and try `List my recent OpusClip projects`.

    For users in more than one OpusClip org, the connector defaults to the first org with API access. To target a different org, ask the agent to list your orgs and select one; the choice applies to subsequent requests in the same conversation.

    **Claude Code, Cursor, and other MCP hosts**

    Configure the host with the endpoint above. Complete the OAuth flow when prompted.

    #### Tool catalog

    The connector exposes 25 tools.

    <AccordionGroup>
      <Accordion title="Read tools (13) — no approval prompt">
        * `opusclip_whoami` — identity check for the connected org
        * `opusclip_list_orgs` — list the OpusClip orgs the user belongs to
        * `opusclip_get_usage` — show the org's current API usage against its cap
        * `opusclip_list_projects` — list recent clip projects
        * `opusclip_list_clips` — list clips inside a project
        * `opusclip_describe_clip` — fetch a single clip's detail (transcript, layout, render status)
        * `opusclip_list_collections` — list collections
        * `opusclip_list_clips_in_collection` — list clips inside a collection
        * `opusclip_list_brand_templates` — list brand templates
        * `opusclip_list_social_accounts` — list connected social accounts
        * `opusclip_get_editing_script` — fetch a clip's editing script
        * `opusclip_get_transcript` — fetch a project's source-video transcript
        * `opusclip_get_social_copy_job` — fetch a social copy job
      </Accordion>

      <Accordion title="Write tools (12) — approval prompt per call">
        * `opusclip_submit_project` — clip a YouTube or Vimeo URL · consumes credits
        * `opusclip_create_upload_link` — get a signed URL to upload a local video
        * `opusclip_apply_editing_script` — modify a clip and re-render · consumes credits
        * `opusclip_create_censor_job` — bleep or mask flagged content · consumes credits
        * `opusclip_share_project` — make a project publicly viewable
        * `opusclip_create_collection` — create a collection
        * `opusclip_add_clip_to_collection` — add a clip to a collection
        * `opusclip_export_collection` — export a collection as a zip
        * `opusclip_create_social_copy_job` — generate platform-specific social copy
        * `opusclip_create_post_task` — post a clip to a connected social account
        * `opusclip_schedule_publish` — schedule a clip for future posting
        * `opusclip_unschedule_publish` — cancel a previously scheduled post
      </Accordion>
    </AccordionGroup>

    #### Troubleshooting

    <AccordionGroup>
      <Accordion title="OAuth fails or returns 'No matching client'">
        Sign in with the same identity provider used to create the OpusClip account (email, Google, or Apple).
      </Accordion>

      <Accordion title="Tools return 'API access not enabled for this org'">
        The org does not have the API entitlement. Pro Beta and Max orgs receive it automatically. Otherwise, [contact sales](https://www.opus.pro/contact-api).
      </Accordion>

      <Accordion title="Which org does the connector use for a multi-org user?">
        The first org with API access. To target a different org, ask the agent to list your orgs and select one; the choice applies for subsequent requests in the same conversation.
      </Accordion>

      <Accordion title="401 errors keep firing">
        Hosts refresh tokens automatically. If refresh fails persistently, remove the connector and re-add it.
      </Accordion>

      <Accordion title="403 or 429 responses">
        `403` indicates the monthly cap (`15h` / `900` credits per workspace) has been hit. The cap resets on the first day of the next month (UTC). `429` indicates the concurrent-project limit (`4`) has been hit and clears as in-flight projects finish. See [Limitations](/api-reference/limitation).
      </Accordion>
    </AccordionGroup>

    Tools consume credits and inherit the Pro Beta & Max caps (`15h` monthly, `10`-credit per-project floor, `4` concurrent projects). See [Limitations](/api-reference/limitation).

    ***

    ### Skill

    A code package the agent loads. It documents how to call the OpusClip API and includes worked samples the agent adapts at runtime.

    Get an API key from the [OpusClip dashboard](https://clip.opus.pro/dashboard) under **API Access → Create key**. Set it in the shell that launches the agent:

    ```bash theme={"dark"}
    export OPUSCLIP_API_KEY=sk-...
    ```

    <Warning>
      Do not paste API keys into chat with the agent. Chat content can be retained in transcripts, logs, and model context. Set the key in the shell environment as shown above.
    </Warning>

    Install the skill in your host:

    **Claude Code**

    ```text theme={"dark"}
    /plugin marketplace add opus-pro/opus-skills
    /plugin install opusclip@opus-skills
    ```

    **Codex (CLI and App)**

    ```bash theme={"dark"}
    codex plugin marketplace add opus-pro/opus-skills
    ```

    **OpenClaw**

    ```bash theme={"dark"}
    openclaw plugins install clawhub:opusclip-pro
    ```

    **Claude.ai Web and Claude Cowork (Pro+ Anthropic subscription)**

    * Clone the repository:

    ```bash theme={"dark"}
    git clone https://github.com/opus-pro/opus-skills.git
    ```

    * `cd skills && zip -r opusclip-skill.zip opusclip`
    * Upload the zip at **Settings → Customize → Skills**.

    **Other hosts with npx skills**

    ```bash theme={"dark"}
    npx skills add opus-pro/opus-skills
    ```

    **Verify installation.** Start a new conversation and run:

    > List my recent OpusClip projects

    The agent should call the skill and return a list (or report that the API key is missing). If nothing happens, confirm the plugin loaded and that `OPUSCLIP_API_KEY` is set in the shell that launched the host.
  </Step>

  <Step title="Try it">
    **Clip a video**

    > Clip this YouTube video and give me the top 5 best clips
    > `https://youtube.com/watch?v=...`

    **Inline edits**

    > Fix the typo in caption 4 of clip 3.
  </Step>
</Steps>

## What's next

* Marketplace listing and security work at [skills.sh](https://skills.sh).
* Need higher limits? [Contact sales](https://www.opus.pro/contact-api).
* On a **Business** plan? Your custom limits live in your contract. Talk to your account manager for details.
