Motionmaxxing with Claude Code means adding the Creator OS MCP server to Claude Code, then driving motion edits and publishing the finished cut from the same terminal session. You install one command, authenticate with a cos_live_ API key, and ask Claude Code to build the edit and post it to X, LinkedIn or YouTube.
Claude Code terminal
|
| 1. claude mcp add ... creatoros
v
Creator OS MCP server (https://mcp.creatoros.ca/mcp)
|
| 2. create_post, upload_media_from_url
v
Your workspace: X, LinkedIn, YouTube, Instagram...
^
| 3. motion edit skills run locally
|
Raw clip --> captions, logos, b-roll --> finished cutWhat Motionmaxxing With Claude Code Actually Does
Motionmaxxing with Claude Code splits one job into two halves: the edit happens on your machine, the publish happens through Creator OS.
The edit half is open source. OPEN VIDEO EDIT (github.com/kevinbadi/open-edits) is a set of Claude Code skills that turn a raw talking-head clip into an animated short: captions, logos, faces, GIFs, b-roll cards and counters. It renders locally with Python and ffmpeg. Skills include split-animated-talking-head, longform-animated-talking-head, fireship-style-edit, fireship-style-short, split-animated-short and reverse-engineer.
The publish half is the Creator OS MCP server. It is hosted at https://mcp.creatoros.ca/mcp and nothing needs installing on the server side. Once connected, Claude Code can call tools like create_post, upload_media_from_url, get_post_analytics and get_best_time_to_post without you leaving the chat.
What you get is a single conversation that reads your clip, applies a motion template, writes the caption, checks the length, uploads the file once as a med_ id, and schedules the post. No tab switching, no manual re-upload per platform.
If you want the background on the skills themselves, the motionmaxxing agent skill walkthrough covers what each skill does to a clip.
How to Get Claude Code (and Where the claude code docs Live)
You need Claude Code installed and a Creator OS API key before anything else works.
Install Claude Code from Anthropic, sign in, and confirm it runs with a quick prompt. The Creator OS side is documented at https://www.creatoros.ca/docs/claude-code, which covers the plugin, the MCP entries and the configuration questions. The general MCP reference lives at https://www.creatoros.ca/docs/mcp.
Two setup paths exist, and they suit different people:
| Path | Command | What it adds |
|---|---|---|
| MCP server only | claude mcp add --transport http creatoros https://mcp.creatoros.ca/mcp --header "Authorization: Bearer cos_live_..." |
All MCP tools, roughly 160 of them |
| Plugin | /plugin marketplace add kevinbadi/creatoros-claude-plugin |
MCP server plus campaign builder skills, a live pane, /cos-stats, /cos-health and a publish guard |
The plugin route also needs /plugin install creatoros@creatoros and /plugin configure creatoros@creatoros, which asks for the cos_live_ key. The plugin mod requires Claude Code 2.1.287 or later. Its publish guard asks Proceed or Cancel before anything is published, spent or deleted, which matters once an agent is posting on your behalf.
Kevin walks through the terminal setup on the KevBuildsApps YouTube channel if you prefer watching the commands run.
How to Add the Creator OS MCP Server to Claude Code
The one-line add command is the whole install for the server, and the key is the only secret you manage.
- Open Settings, then API keys, on Creator OS and create a key. It starts with cos_live_ and is pinned to one workspace.
- Run the add command above with your key in the Authorization header.
- Start a Claude Code session and ask it what Creator OS tools it has. If create_post shows up, you are connected.
A few details that matter for agents. Read-only keys are available in Settings, and the API refuses writes from a read-only connection. Each connection gets its own key, listed under Settings, then Connected apps. Destructive tools such as delete post, delete comment and delete automation are marked so the AI app asks first.
Scoping is workspace level. An agent holding one workspace’s key cannot post to another workspace. On agency plans you connect one client per connection, which keeps client work separated without extra config.
Step 1: Authenticate Creator OS From the Terminal
Authenticate once from the CLI, then let the MCP session reuse the workspace.
creatoros auth:check
creatoros profiles:list
creatoros accounts:list
creatoros accounts:healthThe CLI is @creatoros/cli. auth:check confirms your key works, profiles:list shows which workspace you are pointed at, and accounts:list returns the social accounts you can publish to along with their acc_ ids. Run accounts:health if a platform has not posted in a while, since a disconnected account silently drops out of a post.
Inside Claude Code, the equivalent is asking the agent to run platform_read or simply listing connected accounts through a tool call. If you have not set up the CLI yet, creatoros init writes the config for you.
Now you have the two ids a motionmaxxing session needs: the workspace, and the acc_ id for wherever the finished short goes.
Step 2: Pull a Source Clip Into the Motionmaxxing Session
Get the raw file into a place both Claude Code and Creator OS can read.
The edit skills work on a local file path. Point Claude Code at the clip on disk, then have it upload the same file to Creator OS so the publish step has a stable media id:
creatoros media:upload ./clips/talking-head-raw.mp4That returns a med_ id you can reuse on every platform. The MCP equivalent is upload_media_from_url, which works when the clip already lives at a URL. Uploading once and reusing the med_ id is faster than attaching the file again for each network.
Run creatoros validate:media --url <url> first if the clip is hosted, so you find out about a bad codec before the render finishes. There is nothing worse than a 12 minute edit that fails at the upload step.
One file, one id, every destination. That pattern is what makes the rest of the loop short.
Step 3: Run Motion Edits With a Claude Code Prompt
A specific prompt does more work than a vague one, so describe the template, the length and the platform in the first sentence.
Here is a prompt that works for a short:
Use the split-animated-short skill on ./clips/talking-head-raw.mp4.
Keep it under 45 seconds, 9:16, captions burned in,
add a b-roll card at the product mention and one counter
at the price. Render locally and show me the output path.For a longer cut, swap in longform-animated-talking-head or fireship-style-edit. The skills render with Python and ffmpeg on your machine, so nothing leaves your laptop at the render step and there is no render queue to wait on.
Before you publish, have the agent check the caption against the platform limits. The MCP tool check_caption_length does this per network, and creatoros validate:post-length --text "your caption" does the same from the CLI. Threads caps posts at 500 characters, for example, and YouTube titles stop at 100 characters, so a caption written for X may need trimming for another target.
If you want a hook suggestion, ask for one and make the agent show the analytics that justify it. get_best_time_to_post and get_post_analytics are both available as tools, so the agent reads your own account history instead of guessing.
Step 4: Post the Finished Cut Through Creator OS
Publishing is one tool call once the med_ id exists, and the same cut can go to several networks with per platform options.
Ask Claude Code directly:
Publish the rendered short. Use med_abc123 as media,
caption below, to X and LinkedIn. Schedule it for tomorrow
at 9am Eastern, and add a first comment on LinkedIn with
the newsletter link.From the CLI, the same action is:
creatoros posts:create --text "Motionmaxxing in one take." \
--platforms twitter,linkedin --media med_abc123 \
--scheduledAt 2026-05-14T13:00:00Z --timezone America/New_YorkPlatform rules are applied for you. Creator OS handles Shorts and Reels formats, TikTok consent flags and the rest of each network’s requirements. If you name a network that is not connected, the response lists it in missing_platforms and the connected ones still go out, so a missing account does not block the whole post.
After publishing, get_post_analytics and get_daily_metrics close the loop. Ask the agent to pull engagement after 48 hours and tell you which frame held attention, then feed that answer into the next edit prompt. That feedback cycle is the actual motionmaxxing habit: edit, publish, read, repeat.
For the full post options reference, see https://www.creatoros.ca/docs/post-options.
Using motionmaxxing github and editing os claude Resources
Three open resources do most of the heavy lifting, and none of them lock you in.
- OPEN VIDEO EDIT at github.com/kevinbadi/open-edits holds the Claude Code skills for talking-head edits, captions, b-roll and counters.
- Social Agents at github.com/kevinbadi/social-agents is an open-source agent harness that runs your socials on Creator OS. Start it with
npm start creatoros social-agents. It interviews you about your brand, then posts, replies to comments and DMs, runs automations and reports, with a local dashboard. You bring your own model: a logged-in Claude Code session, an ANTHROPIC_API_KEY, or any Anthropic-compatible API. - The Creator OS plugin repo at github.com/kevinbadi/creatoros-claude-plugin holds the plugin, its skills and the publish guard mod.
Creator OS does not ship its own model. It works with any MCP-capable AI app or agent, and the site names Claude, ChatGPT, Cursor, Gemini, Ollama, Grok, Hermes, OpenClaw and Jev. Current Claude models include Claude Opus 5.5, Claude Sonnet 5.5, Claude Haiku 4.5 and Claude Fable 5.1, and any of them can drive this loop.
The Creator OS launch video shows the publish side end to end if you want the visual version.
FAQ
How to set up motionmaxxing with Claude Code?
Install Claude Code, create a cos_live_ key in Creator OS, and run the claude mcp add command with the MCP URL and the Authorization header. Then install the OPEN VIDEO EDIT skills, point Claude Code at a raw clip and name a skill in your prompt. The full reference is at https://www.creatoros.ca/docs/claude-code.
Where is the motionmaxxing github repo?
The motion edit skills live in github.com/kevinbadi/open-edits, which is the OPEN VIDEO EDIT project. The Creator OS side is github.com/kevinbadi/creatoros-claude-plugin, and the agent harness is github.com/kevinbadi/social-agents. All three are open source and separate repos.
Can Claude Code post motion edits to X and LinkedIn?
Yes. Once the MCP server is connected and the media is uploaded as a med_ id, a single create_post call can target X and LinkedIn together, with per platform options where they differ. A read-only connection cannot publish, and the plugin’s publish guard asks Proceed or Cancel first.
What claude code docs do I need for MCP servers?
Start with the Claude Code plugin page at https://www.creatoros.ca/docs/claude-code and the MCP page at https://www.creatoros.ca/docs/mcp. For keys and scoping, read https://www.creatoros.ca/docs/authentication. The posts API reference at https://www.creatoros.ca/docs/api/posts covers request shapes if you drop to raw HTTP.
Do I need the original motionmaxxing agent skill before this?
No. The OPEN VIDEO EDIT skills are the motion side, and the MCP server is the publish side, so you can add either first. Reading the earlier walkthrough helps you pick the right skill for a clip, but the setup here stands on its own.
Get Started With Creator OS MCP
Connect the server, install the skills, and you can go from a raw clip to a scheduled post without opening a browser tab.
Create a key, run the add command, and start with one platform before adding more. If a session gets confusing, ask the agent to list its Creator OS tools and run creatoros auth:check to confirm the workspace.
Creator OS plans start at $14.99/month for 11 platforms plus Skool, with the API, the MCP server and the CLI included. New subscribers start for $0 with a free trial and can cancel anytime. Sign up at https://www.creatoros.ca/sign-up, and watch the walkthroughs on the KevBuildsApps YouTube channel.
Get started for $0
Free trial for new subscribers. Cancel anytime.