Add Flixly as an app/plugin in ChatGPT, a connector in Claude, or an MCP server in Cursor and other clients. Give it a text brief for an image or short video and it uses one of six curated models with your existing Flixly credits.
https://www.flixly.ai/api/mcpAdd this in your client's app, plugin, connector or MCP settings. You'll be asked to sign in once.
Pick where you want to use it.
Five narrow tools cover model discovery, text-to-image, text-to-video, same-job result retrieval and your available credit balance.
list_modelsBrowse the reviewed image-and-video set, including model ids, estimated credit cost and supported settings.
generate_imageCreate an image from a text brief. The completed image is shown inline in the conversation.
generate_videoCreate a short video from a text brief. Returns one task id that the client follows until the render is ready.
get_generationCollect the result of a generation that was still rendering. Free to call.
get_accountRead the credits currently available for generation.
Try asking:
Same pricing
MCP generations cost exactly what the REST API and dashboard cost. No surcharge.
Auto refunds
A failed generation returns its credits automatically — you are never charged for a broken render.
Server-enforced limits
Rate limits and parallel job limits are enforced by Flixly and shared with the REST API.
Data access and generation history
A connected client can browse the curated model and estimated-cost metadata, read your available credit balance, submit image or short-video generations, and poll their status and outputs. It cannot retrieve passwords, payment details, session tokens or API-key values. MCP jobs appear in your Flixly generation history. Generated output files are hosted for 30 days and then automatically deleted; download files you want to keep. The prompt, model, settings and other history metadata may remain after the file expires.
Do I need an API key?
No. In ChatGPT you connect the Flixly app and sign in. Claude, Cursor and other remote-MCP clients take the connector URL and then the same sign-in — approve once, done. An API key is only needed for the stdio bridge, which exists for clients that can't reach a remote server.
How do I disconnect?
Remove Flixly from the client's app, plugin or connector settings, then revoke the dedicated credential under Flixly Dashboard → Settings → API keys. Revocation stops future MCP access immediately.
What does it cost?
The same credits as the rest of Flixly — nothing extra for MCP. Ask the model to check list_models before generating and it will tell you the cost first. Failed generations are refunded automatically.
Why did my video come back as a task id?
Video takes 30-300 seconds, which is longer than a single tool call should block. The job is already submitted and paid for; one attached result card checks the same task id and displays the video when it is ready. Do not regenerate while that card is processing.
Can I upload a photo, video or other media as input?
No. This reviewed v1 accepts text briefs only. Source-media transformations, audio, identity transformations and 3D workflows are not exposed through this connection.
Which models are available?
list_models returns the curated v1 set: Nano Banana 2, Ideogram V4 and Z-Image for images; Kling 3.0 Turbo, Hailuo 2.3 Standard and Runway Gen-3 Turbo for short videos. The wider Flixly studio is separate and is not exposed through this connection.
What account data can a connected client access?
The granted Flixly scopes let it browse curated model details and estimated costs, read your available credit balance, submit image or short-video generations, and poll their results. Tool responses do not expose passwords, payment details, session tokens or API-key values.
Where are MCP generations saved?
They appear in your Flixly generation history like dashboard jobs. Generated output files are hosted for 30 days and then automatically deleted, so download anything you want to keep. History metadata such as the prompt, model and settings may remain after the media expires.