Framesail MCP Server

According to the provider, Framesail MCP Server is an independent remote MCP service for producing long-form, faceless YouTube videos. On its official developer site, Framesail describes itself as a workflow and state layer: the product manages projects, style settings, asset continuity, voice timing, storyboard planning, and the render pipeline while a compatible AI agent drives the workflow. The provider endpoint is https://api.framesail.com/mcp. The official repository at https://github.com/framesail/framesail-mcp documents this hosted server, confirms its relationship to Framesail, and explicitly says that the service itself is closed source. Smithery lists framesail/framesail as a remote deployment at https://framesail--framesail.run.tools. That Smithery endpoint returned HTTP 401 during an anonymous probe and pointed to Bearer authorization. This is an access boundary, not evidence that the service is absent. The independent provider source maps the remote service unambiguously to api.framesail.com/mcp; the Smithery entry is therefore directory and deployment metadata, not the sole basis for identity.

Provider identity and actual scope

Framesail names cofounders Jordan and Hayden as its operators on the About page. The official developer documentation describes MCP and REST access and a workflow covering style and project management, scripting, references, voiceover, storyboarding, scene construction, and export. The repository names channels and projects, reusable styles, script generation and saving, scanning characters, environments, and objects, consistent reference images, voice assignment, word-timed voiceovers, scene animation, assembly, and MP4 export. It also exposes account information, credit balance, and job status. The documented scope is, according to the provider, durable and independently useful. According to the provider, server-side guardrails enforce the order of production steps, prevent duplicate jobs while work is running, and return corrective guidance when prerequisites are missing. Tool responses and generated media still require review: stylistic consistency, rights to source material, voices, music, images, and video references are not guaranteed by this catalog entry.

Data provenance and authorization

Processed design, product, and company data typically comes from the Framesail account, user-created channels and projects, uploaded or linked style and reference material, entered video briefs and scripts, and model or media services integrated by the provider. A YouTube URL or image is not proof of ownership. Before processing, users must hold the required rights, consents, and internal approvals. OAuth 2.1 with Dynamic Client Registration and PKCE, or a user-managed Bearer key, limits the connection to an authorized account; this catalog stores no keys, tokens, credentials, or personal data. Roles should separate agent and human accounts, minimize project permissions, and use revocable connections. The provider describes account-level connection management and revocation, but current policies, retention, and subprocessors must be checked directly before production use.

Privacy, sharing, and write access

The remote server receives requests and may process project content, scripts, assets, voice settings, production status, and downloadable media. Downstream model and media services may receive that content to generate text, images, audio, or video; a connected AI model may also see the supplied context and responses. Organizations should document privacy boundaries and data sharing responsibilities, then apply data minimization, TLS, endpoint allowlisting, short retention, controlled logs, and a review of provider terms. The scope is not read-only: channels, projects, scripts, assets, voices, scenes, render jobs, and exports can be created, changed, or deleted. These include potentially persistent and credit-consuming production actions. Apply least privilege, explicitly confirm destructive or publishing steps, and review trademark, copyright, personality-rights, and platform rules before export. According to the provider, Framesail is a durable product with an official website, documentation, provider repository, and canonically named remote endpoint. This E-E-A-T basis supports identity and documented scope, not the quality of every generated result or legal permission to publish it.

A compatible MCP client with Streamable HTTP support, a Framesail account with MCP access enabled, and verified rights to all supplied content.

Add the official remote endpoint https://api.framesail.com/mcp to the MCP client and use OAuth or a protected, short-lived account connection according to current Framesail documentation. Verify connection and permissions before production writes or exports.

https://api.framesail.com/mcp

According to the provider, OAuth 2.1 with PKCE or Bearer authentication using an fsk prefix is supported. Do not store keys, tokens, or credentials in the catalog; manage and revoke connections by account and role.

According to the documentation, the service can read, create, change, or delete channels, projects, scripts, assets, voices, scenes, render jobs, and exports. Write and publishing actions require least privilege and human confirmation.

Remote processing of project, script, asset, voice, status, and media data. Content may be shared with connected model and media services and, through the client, with a language model, logs, or telemetry.

Risks include prompt injection, unauthorized account actions, permanent deletion, unintended exports, sensitive data sharing, copyright violations, and faulty generated media. Mitigate with allowlisting, roles, confirmation, and source review.