FLORA MCP documentation
Connect FLORA to Claude, Claude Code, ChatGPT, Codex, Cursor or any MCP client so your agent can generate, run Techniques and build on your FLORA canvases.
FLORA MCP is FLORA's hosted MCP server. Connect it once and your AI agent can generate images, video, audio, text and 3D, run your team's Techniques, and put the results on your FLORA canvases. These docs cover installing it, what each tool does, and the rules your agent follows.
Server URL
https://agents.flora.ai/mcp (no trailing slash)
Transport
Streamable HTTP. It's a remote server, so there's nothing to install.
Sign-in
OAuth with your FLORA account. Headless clients can send a FLORA API key as Authorization: Bearer <key> instead.
Server name
flora
Check it works
Ask your agent: "List my FLORA workspaces. Don't generate anything."
Who can connect: API and MCP are included from Starter up. A Free account can also connect and generate on the $2.50 of usage every new workspace gets. Each generation is billed in US dollars to the workspace you choose. See How FLORA pricing works and Authentication.
Skills: tested workflows (batch generation, refine loops, Technique runs and more) live at github.com/florafauna-ai/flora-mcp-skills. Your agent lists them with
flora_discover_skills. See Skills and plugins.For agents: every page here is also Markdown. Append
.mdto any URL, for example https://docs.flora.ai/mcp.md. The full index is https://docs.flora.ai/llms.txt.
Install in your client
New to FLORA MCP? The quickstart takes you from connecting to your first image on a canvas.
Start here: eight tools
Your connection has more tools than these (the list depends on your account, plan and client; flora_list_tools returns the ones you have). Most jobs start with these eight.
Lists the workspaces you can use, and which one you're in. Read-only.
Lists projects (canvases) in a workspace. Read-only.
Lists models with their model_id, estimated cost and parameters. Read-only.
Starts 1 to 20 generations on a canvas, or quotes their cost with quote: true. Spends money.
Reads up to 20 runs by run_id, or lists history. Read-only.
Brings your own files into FLORA from a URL or an upload link.
Runs one of your team's Techniques. Spends money.
Reads balance and spend in US dollars for a workspace or organization. Read-only.
The full list, with arguments and examples, is in the tools reference.
What your agent can do
Make an image, video, audio clip or 3D model from a prompt or references
Animate a product photo
Make 20 to 500 assets from a list or sheet
Run a Technique your team built
Use your own images, video, audio or PDFs
Lay results out on a canvas
Make more like the ones you liked
Get better results from your prompts
All recipes are indexed in Recipes.
Tool sequences for common jobs
First image
flora_list_workspaces → flora_list_projects (or flora_create_project) → flora_create_generations with quote: true → approval → flora_create_generations → flora_list_generations
Video from a photo URL
flora_list_workspaces → flora_list_projects → flora_list_models with the video model_id (to read its image field name) → quote → flora_create_generations with the URL in params → flora_list_generations
Cost and balance
flora_list_models (estimated_cost_usd) or a quote: true call → flora_get_usage
Run a Technique
flora_list_techniques → flora_get_technique → flora_run_technique → flora_list_generations with run_ids and technique_id
Use a local file
flora_create_asset with source: "signed-url" → upload (shell) or upload_page link (chat) → flora_complete_asset
Grid on a canvas
flora_get_canvas → flora_arrange_canvas with node_ids and layout, or all: true alone
Animate a canvas image
flora_add_to_canvas (video node wired to the image) → flora_run_canvas_nodes → flora_list_generations
Rules your agent follows
The server gives agents these rules. They're here so you know what to expect, and so you can hold your agent to them.
Ask which workspace to bill. A connection isn't tied to one workspace. If several come back from
flora_list_workspacesand none is current, the agent names them and asks you which to bill. Project tools bill the project's own workspace.Quote first, in US dollars. The agent calls
flora_create_generationswithquote: true, shows you the cost in US dollars (never credits), and runs the same request withoutquoteonly after you approve.run_costandcharged_costare dollars:0.009means $0.009. A failed run isn't charged; a retry is a new run and is billed again. Details: Cost, balance and limits.Stop on billing errors. On
insufficient_creditsor anyBILLING_*error, the agent stops and passes the message on. It doesn't retry.paid_plan_requiredmeans the workspace's plan doesn't include what was asked. Balance and spend come fromflora_get_usage.Poll slowly, in one call. The agent saves every
run_id, waitsmax(15, 2 × number of runs)seconds between polls (15 seconds for up to 7 runs, 40 seconds for 20), and reads all of them in oneflora_list_generationscall (up to 20run_ids, plustechnique_idfor Technique runs). Faster polling returns429or cooldown errors withretry_after_seconds. Details: Runs.Never re-fire a partial batch. Items that started already cost money, and a timed-out call may still have started a run. The agent reads history before trying again. See Runs.
Link with
canvas_url. The agent opens results with thecanvas_urleach generation returns and never builds project links from IDs.
FLORA MCP, fal, Replicate or a model provider's API?
Model APIs and aggregators like fal and Replicate return a model's raw output to your code. FLORA MCP is built for creative work with an agent:
Results land on a canvas. Every generation becomes a node on a FLORA project your team can open, compare, edit and build on, not a file URL in a chat log.
Your team's workflows come along. Your agent can run the Techniques your team saved, and use FLORA's skills.
Team billing and controls. Workspaces, members, roles, per-workspace spend limits and usage reporting apply to agent runs too. Prices are FLORA's published per-generation rates on Model Pricing, the same as in the app.
One connection, many model families. Image, video, audio, text and 3D models from several providers behind one sign-in.
If you only need one model's output inside your own app, with no canvas or team workspace, a provider's API or an aggregator may fit better. To call FLORA from your own code, use the FLORA API.
Terms
Workspace
Where projects live and where usage is billed. You can belong to several. IDs look like ws_123.
Project
One FLORA canvas and its contents. IDs look like prj_abc.
Canvas
The board inside a project where nodes sit and connect.
Node
One block on a canvas: an image, video, text, Technique or other step. Generations land as nodes.
Run
One generation or Technique execution, tracked by its run_id.
Technique
A saved, reusable workflow your team built in FLORA. See Techniques.
Asset
A file in FLORA, uploaded or generated, with an asset_id.
Skill
Written instructions an agent follows for a bigger job, listed by flora_discover_skills.
Everything in these docs
Quickstart: connect, check, and make your first image.
Install: steps for every client.
Authentication: OAuth, API keys, workspaces, and disconnecting.
Cost, balance and limits: quotes, balance, and billing errors.
Runs: polling, timeouts and failures.
Recipes: step-by-step jobs.
Tools reference: every tool and its arguments.
Skills and plugins: tested workflows and how to install them.
Troubleshooting: symptoms, causes and fixes.
Security and data: what leaves FLORA and what your agent can do.
Changelog: what changed and when.
Retired tools: older tool names and what replaced them.
FLORA API: call FLORA from your own code with an API key.
Watch: Everything About FLORA MCP
Need help? Email [email protected].
Last updated
Was this helpful?