Schedule clips from chat, with a human check

Marketing content & social · checked 2026-10-17

OpusClip’s MCP server includes posting and scheduling tools. On the self-configured server those commit directly, so ask the agent to propose a schedule and approve it before it calls them.

Independent review. IonBin has no partnership with any tool on this page and was not paid for this page. Our evaluation is our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.

Goal

Schedule a week of clips in one conversation without surprises.

Connects through: MCP

Steps

#WhoWhat happensHowStatus
1Claude Proposes a posting schedule AI platform Confirmed
2You Approve the schedule Human step Confirmed
3OpusClip Schedules the approved posts MCP Confirmed · source ↗

Confirmed means the vendor documents it (linked). It doesn't mean IonBin has tested it. AI-platform and human steps need no source.

Human approval

You approve the schedule before any posting tool runs.

Watch out for

On mcp.opus.pro, posting and scheduling tools commit directly. The Claude Connector version asks for confirmation in OpusClip instead.

Starter prompt

Goal: Schedule a week of clips in one conversation without surprises. Tools involved: Claude, OpusClip. Your part: proposes a posting schedule; schedules the approved posts. Work step by step, show me each draft or proposed change, and wait for my approval before anything is sent, published, signed, filed or changed in a live system.

Assembled from this page’s goal and steps. Paste it into your AI platform and adjust it to your situation.

Tools in this workflow

ToolRoleOfficial site
ClaudeAI platform claude.ai ↗
OpusClipMCP opus.pro ↗

Which AI platforms can run it

PlatformStatusWhy
Claude (incl. Claude Code) Confirmed Every MCP and API step is documented for this platform.
OpenAI Codex Confirmed Every MCP and API step is documented for this platform.
Google Antigravity To verify OpusClip: pairing not named in vendor docs
ChatGPT Confirmed Every MCP and API step is documented for this platform.
Gemini To verify OpusClip: pairing not named in vendor docs
Perplexity To verify OpusClip: pairing not named in vendor docs

Computed from the MCP and API steps only: "Confirmed" needs the tool's docs to name the platform and the platform to support the connection. Browser, upload and human steps work from any platform.

What we checked (2026-10-17)

  • OpusClip MCP (mcp.opus.pro/mcp) signs in with OAuth. Any account can view the tool catalog, but calling tools needs Pro (Beta), Max or Business plan access.
  • Read tools run without an approval prompt. They include opusclip_list_social_accounts and opusclip_list_scheduled_posts.
  • Posting, scheduling, unscheduling and project sharing commit directly on mcp.opus.pro, because you configured it yourself. The Claude Connector version exposes the same tools, but those four return a link you confirm in OpusClip instead. Don’t assume a prompt behaves the same on both.
  • Connected accounts. Social accounts are connected in OpusClip, and posting to X uses 3 credits per post. We didn’t find a per-plan limit on connected accounts in the docs we checked.

Set it up

  1. Ask the agent to list your connected social accounts and the clips you want to post.
  2. Have it propose a schedule as a table with clip, platform, date, time and caption. Tell it not to call any posting tool yet.
  3. Edit the table and reply “approved”, or use the Claude Connector so each post needs a confirmation in OpusClip.
  4. After scheduling, ask it to list scheduled posts and compare them with your table.

Sources

Related workflows

No affiliate links on this page. No paid placements in workflows. How IonBin makes money.