Cursor connection status
StoryStudio in Cursor: MCP connection status
Connection status — 15 September 2026: First-time OAuth with StoryStudio in Cursor has not yet been validated end to end. StoryStudio responded in an existing Claude session on this date; that test did not validate a first OAuth connection from a new account, or a connection in Cursor or Claude Code.
StoryStudio offers image, video and audio generation through MCP. This page explains what to check before trying a connection from Cursor.
A workflow to evaluate
If you write product code in Cursor, you may also need demo footage, marketing stills or a product-launch video. The workflow to evaluate is requesting those assets from the editor through StoryStudio. Authorization, tool access and retrieval of the generated result all need to work before you can rely on it.
Before trying the connection
Use the StoryStudio connection section to find the MCP endpoint. If you try adding it to Cursor, check that authorization completes and that StoryStudio's tools appear. Then verify the full workflow with a generation request and confirm that you can retrieve the result. Adding the endpoint alone does not confirm a working connection.
What StoryStudio offers
Images, video (image-to-video and text-to-video), voice-over, music, and a timeline editor with MP4 export for anything that needs a few shots stitched together.
FAQ
Has first-time OAuth been validated in Cursor? Not yet end to end. The 15 September 2026 test used an existing Claude session, so it does not establish first-time OAuth compatibility with Cursor or Claude Code.
Has a first connection from a new account been tested? The existing Claude session test did not cover that case. A successful response in an already connected session does not establish that a new account can complete OAuth.
Will the generated result appear directly in Cursor? That part of the workflow still needs verification in Cursor. Check that you can retrieve the generated asset before depending on an in-editor workflow.