Account, billing & API

MCP server & connecting agents

Framesail ships a remote MCP server at https://api.framesail.com/mcp (streamable HTTP — nothing to install), so Claude or any MCP client can drive the whole pipeline: projects, styles, assets, every generation step, audio, scenes, export, and your credit balance. MCP access is included on the Pro, Studio, and Scale plans.

Two ways to connect

• ·API key as Bearer token — for clients that let you set headers (Claude Code, Cursor, plain REST). For Claude Code: claude mcp add --transport http framesail https://api.framesail.com/mcp --header "Authorization: Bearer fsk_YOUR_KEY".
• ·OAuth click-to-connect — for clients that can't send headers (claude.ai, Claude Desktop, mobile). Add the connector URL, approve the consent screen in your browser, done. Under the hood this is standard Dynamic Client Registration + PKCE, and the issued access token is a regular fsk_ key — so you revoke an agent's access from the account page like any other key.

On plans with API access, the API keys section of your account page has a "Connect an agent" block with the exact steps for both paths.

Guardrails agents get for free

Step order is enforced server-side: a tool called before its prerequisites are done fails with a self-correcting error that names the exact next action, so agents recover instead of flailing. Re-submitting a step that is already running is refused rather than double-billed, and batch steps skip items already generated or in flight — an agent retrying never duplicates work.

Where it's listed

The server is listed on Smithery, Glama, and GitHub. For the broader developer surface — the REST API behind the same keys — see API keys & the REST API and the developers page.