Post Reels and Shorts from Codex.
Two commands add Motion Reel's MCP server to Codex and sign you in, and the Codex CLI, app and IDE extension share the setup. Codex can then send a video from your project, schedule it to Instagram Reels and YouTube Shorts, run comment-to-DM and read the stats, showing you a preview first.
Updated November 17, 2026. Also in Markdown at /agents/codex.md.
Set it up
- 1Have Motion Reel ready. Sign up at motionreel.app (every plan starts with 7 days free and has the MCP server), then connect your Instagram Business or Creator account or your YouTube channel in the dashboard. Your agent can't do that part.
- 2Add the server and sign in. Run these in a terminal. The second opens your browser: sign in to Motion Reel and click Allow.
codex mcp add motionreel --url https://motionreel.app/mcp codex mcp login motionreel
- 3Start a new session. Codex loads its servers when a session starts. The Codex app and IDE extension use the same setup.
- 4Check it worked. Ask Codex to run whoami. It answers with the accounts it can post to.
Then ask it
- “Post out/demo.mp4 as a YouTube Short on Friday at 9 am, unlisted, not made for kids.”
- “Schedule the same video as an Instagram reel an hour later, with a shorter caption.”
- “Turn on comment-to-DM for that reel: the word is DEMO and the DM is this link.”
- “List what's scheduled for next week.”
Every post, change and automation comes back as a preview first. Nothing happens until you say yes.
Good to know
- Signs in with
- Your Motion Reel account. You click Allow once, and there's no key to copy or keep safe.
- Getting a video to it
- Codex runs the upload command Motion Reel gives it, so a file in your project goes up from there. A direct link works as well.
- Where it's kept
- In ~/.codex/config.toml, which the Codex CLI, app and IDE extension share.
- Using a key instead
- Add --bearer-token-env-var to the first command with the name of an environment variable that holds a Motion Reel key, and skip the second.
- How we checked
- The commands are from Codex's own docs, and Codex's published sign-in details pass our sign-in tests (16 Nov 2026). We haven't run it inside Codex ourselves yet: if a step differs, tell us at support@motionreel.app.
- Signing it out
- Each signed-in app shows in the dashboard under Agents & API, named after the app. Revoke it there and it loses access at once.
When something goes wrong
- codex mcp login doesn't open a browser
- Copy the address it prints into your browser, sign in and click Allow.
- Codex doesn't list Motion Reel's tools
- A session that was open when you added the server doesn't have it. Start a new one.
Read next
- Connect CursorAdd Motion Reel to Cursor's mcp.json with a key, and its agent schedules your reels.
- Instagram Reels from ClaudeSchedule reels, answer comments and read each reel's numbers.
- DocsKeys, previews, uploads, errors and every operation with its input.
- Every AI appStep-by-step pages for the other apps, any MCP client, and every tool your agent gets.
Motion Reel