Generate YouTube videos from concept to final MP4 with AI script, storyboard, voiceover and animation.
Framesail automates long-form video production: write scripts from your concept, generate storyboards with AI-planned shots, create voiceovers with character voices, render images and video segments, and export finished MP4s. Supports landscape and portrait formats.
Try asking Muse: "Create a 10-minute YouTube video about sustainable fashion by describing the topic and letting Framesail generate the script, visuals, and narration."
Source: Found in the official MCP Registry (com.framesail/framesail) · First listed September 24, 2026
Each bar is one check, every 15 minutes. Green means it answered. Last checked 40 min ago.
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://api.framesail.com/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Framesail is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
In Claude, open Settings, then Connectors.
Choose Add custom connector, give it a name, and paste the link.
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://api.framesail.com/mcpResponse time at the last check: 197ms. Worked in 100% of checks over 30 days.
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
get_statusWhere things stand and what to do next; start and resume here. Always reports the account: plan, credits, credits held by running jobs, and credits_available to spend. project_id adds the project's settings, each step's state and web link, jobs with readable errors, export_url, nview_imageShow a Framesail image inline: a segment image, reference image, style template or preset preview.get_generation_optionsWhat a generate call can be told to use. models: the allowed models with credit estimates and settings_schema (the valid settings keys); is_default marks the default (the account's saved choice, else Framesail's). Voice and clip models come in families, each with its own default:account_editThe account's default model and settings for one kind of generation, used when neither the call nor the item's prompt editor names one. voice_block needs provider and segment_video needs talking_head: each family keeps its own default.deleteDelete; confirm with the user first. A project or music track is deleted for good; an asset or segment_extra is removed to the bin. project: it and everything in it. asset: a character, environment or object. music_track: a background music track. segment_extra: a segment's soundprojects_readYour channels, or the projects in one channel.projects_editCreate a channel or a project, or change a project's title, brief or video format. A new project takes its channel's style; a channel with no style needs one (style_edit action=create) before anything is generated. Share the returned web_url so the user can follow along.style_readget: the channel style: its references, its fields (art_style, narrative_style, director_style, text_style, any added; script_prompt on request), the summary analysis wrote for each, and templates, the character and environment template images (null: not rendered; a URL: it existstyle_editCreate or change the channel style (one per channel, used by all its projects). create: offer the user two real options, never invented ones. (a) References (best): YouTube links of their channel or of videos whose look they like, or a written description. Analysis starts at oncestyle_generateanalyze: read the references again and rewrite art_style, narrative_style, director_style and text_style, replacing hand edits. template: render one of the style's two template images. Reference images render on them (characters on the character template, environments and objectsscript_readThe active script, its versions, and the script settings (script_target_minutes, voice_mix, visual concept). Show the script to the user before Analyze Script.script_editChange the script or its settings; only revise spends credits. save: replace the active version's text (the old text is lost: show the user the current script first), then run Analyze Script. Notation, never read aloud: `[SCENE: <visual direction>]` as its own paragraph directs tscript_generategenerate: write the script from the brief and the narrative style; each run is a new version (review it with script_read). analyze (Analyze Script): find the script's characters, environments and objects (including any named only in `[SCENE: ...]` directions) and split it into voassets_readThe project's characters, environments and objects, each with its description (what every render follows), reference_image (null: not rendered; view_image it), its image's status (as storyboard_read's: stale when its description changed since it rendered) and, for characters, voiassets_editAdd a character, environment or object that Analyze Script missed, or rewrite one's description. After a description change, render its reference image again (assets_generate asset_ids).assets_generateRender reference images, which keep each character, environment and object looking the same in every segment. Needs both style template images. Without asset_ids it renders every asset with none, skipping ones already rendering, so a repeat never bills twice. Afterwards, view_imavoiceover_readvoices: one engine's voice ids, labels and preview audio, as {groups, voices}. blocks: the voice blocks (narration and dialogue) with their speaker, voice_id (the speaker's voice), audio and any `[SCENE: ...]` direction over them (never spoken), as {blocks, total_duration_ms, allvoiceover_editVoices and voice blocks; free. set_voice: the narrator's or a character's voice; every speaker needs one before the voiceover. rescan_blocks: split the active script into voice blocks again after an edit, assets untouched; blocks whose words are unchanged keep their audio. settinvoiceover_generateGenerate voice block audio. Every speaker needs a voice first, and every asset a reference image. Without voice_block_ids it fills every block with no audio, skipping ones already generating. A model must match the project's voice engine. An existing storyboard retimes to the newstoryboard_readsegments: {total, offset, returned, segments}. Each segment has its segment_number (the handle segment tools take), kind (image, clip, talking head, real photo, B-roll or overlay segment), narration, duration, direction, image_prompt, video_prompt (the motion when animated), medistoryboard_editStoryboard settings, used by the next storyboard run.storyboard_generatePlan the storyboard: every segment, its timing, image and motion prompts, overlays and continuations, following the channel style and any `[SCENE: ...]` directions. Needs the finished voiceover (its timing drives the cuts). It plans images, plus real photos and B-roll when the disegment_editChange one segment without losing renders. Returns the changed segments. set_prompts: write prompts verbatim, no AI rewrite. The renders stay as they are: render the segment again to apply the new prompts. set_continuation: make this segment's image continue an earlier one's (samsegment_restructureChange what a segment is. No render is ever lost: what a change replaces goes to the bin. combine: merge with a neighboring segment. The kept segment's prompts and renders stay over the combined length (a clip too short plays over its image; B-roll too short is refused); the otherenderRender segment images and clips, the biggest spend in the video: always run it with dry_run=true first and get the user's yes on the estimate. generate: without segment_numbers, everything not yet rendered (items rendering are skipped); with them, those segments, finished renderseditor_readscenes: the editor timeline, one scene per segment, as {total, offset, returned, scenes}. music: {tracks}, timed in seconds. audio_library: tracks to add with editor_edit; when nothing matches, it lists the library's moods and genres.editor_editPolish the video in the editor; changes show in the next export. scene_note: edit one scene with a note (move, restyle, add or remove layers and overlays, change the text of a lower third, title card or callout, change motion); spends credits. Returns the changes and skipped_mutaexport_videoRender the finished video from the editor timeline; free. When the export job completes, get_status carries export_url.https://api.framesail.com/mcpNot in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Framesail to help me. It is a free service with an MCP server at https://api.framesail.com/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
At the last check (November 13, 2026, 13:45 UTC) the endpoint was working, answering in 197ms. Over the last 7 days it answered 100% of health checks. It is checked every 15 minutes.
It was screened on September 24, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
It exposes 28 tools, including get_status, view_image, get_generation_options, account_edit. For example, you could ask Muse: "Create a 10-minute YouTube video about sustainable fashion by describing the topic and letting Framesail generate the script, visuals, and narration."
This listing was added from public sources (Found in the official MCP Registry (com.framesail/framesail)). If you build Framesail, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/framesail"><img src="https://musedirectory.ai/badge/framesail.svg" alt="Framesail on musedirectory.ai" width="236" height="40"></a>