Agent + MCP

StoryStudio in Codex: connection requirements

2026-07-02

StoryStudio exposes image, video, voice and music tools over MCP. Using them in Codex requires an authorised connection to your StoryStudio account. The Codex connection is still awaiting an end-to-end first-login test.

Connection status — 15 September 2026

Codex OAuth callbacks require server-side activation. Confirm that Codex access is enabled for the StoryStudio server you plan to use before trying to connect.

The reported test on 15 September showed StoryStudio responding in an existing Claude session. It did not test first-time OAuth login with a new account, or validate a connection from Codex, Cursor or Claude Code.

Trying the connection

Once Codex access is enabled, use the StoryStudio MCP connection information to attempt authorisation. Check that the browser returns to Codex and that StoryStudio's tools are available before relying on the integration for a project.

Possible uses after a successful connection

StoryStudio's tools cover product images, demo clips, voice-over, music and montage. Tool availability and how results appear in Codex still need to be verified in the target session.

FAQ

Is StoryStudio ready to use in any Codex session? The server must have Codex access enabled, and first-time OAuth login still needs end-to-end validation. Adding the MCP endpoint alone does not establish a working connection.

Does the Claude test prove Codex works? No. The reported test used an existing Claude session. Each client's first connection must be tested separately.

Will videos and the editor appear inside Codex? That display behaviour has not been validated in this test. Check tool access and result display in your Codex session before planning your workflow around them.

---

View StoryStudio connection information.