FLORA

FLORA MCP Skills

Workflows for pointing your agent at FLORA and getting real work back — not just tool access.

FLORA's MCP server gives any agent the ability to generate images, video, audio and text, run saved multi-step techniques, and read and write a FLORA canvas. That is the raw capability. This repo is the judgment layer: when to use which model, what the gotchas are, what a good result looks like, and what to do when one comes back wrong.

Skills document tested workflows and measured observations. Model behavior and tool availability can change; check the connected server before following an example.

FLORA maintains these skills and publishes updates here through reviewed pull requests.

---

Install

One command. FLORA's MCP server is hosted, authenticated over OAuth, and needs no API key — the first call opens a browser to sign in.

Claude Code

claude mcp add --transport http flora https://agents.flora.ai/mcp

Codex

codex mcp add flora --transport http https://agents.flora.ai/mcp

Cursor, Windsurf, Zed, and other MCP clients — add to your MCP config:

{

"mcpServers": { "flora": { "type": "http", "url": "https://agents.flora.ai/mcp" } } }

Claude.ai (web and desktop) — add it as a custom connector:

1. Copy https://agents.flora.ai/mcp
2. Go to Settings → Connectors → Add custom connector (direct link)
3. Paste, sign in, and start generating

ChatGPT — FLORA is in the app directory; enable it there.

Then add the skills

The server is the capability; the skills are how your agent knows what to do with it.

Claude Code — one command, skills and server together. This repo is also a plugin marketplace, so installing it wires up the MCP server _and_ every skill:

claude plugin marketplace add florafauna-ai/flora-mcp-skills

claude plugin install flora-mcp-skills@flora

Any other agent — copy the skills in:

git clone https://github.com/florafauna-ai/flora-mcp-skills.git

cp -r flora-mcp-skills/skills/* .codex/skills/ # Codex cp -r flora-mcp-skills/skills/* .cursor/rules/ # Cursor

Claude.ai — there is no plugin install, so pick one of three. claude plugin is Claude Code only; on web and desktop the skills go in by hand.

_A Project, if you use FLORA regularly._ Create a Project, open Set custom instructions, and paste in the contents of the skill you want — for example skills/flora-batch-generate/SKILL.md. Every chat inside that Project then has it, with nothing to re-paste. This is the most reliable option and it costs nothing.

_Upload it as a Skill, for something reusable across Projects._ Claude.ai takes a zipped skill folder, and this repo's layout is already the right shape — one directory per skill with a SKILL.md inside it. Zip the one you want:

git clone https://github.com/florafauna-ai/flora-mcp-skills.git

cd flora-mcp-skills/skills && zip -r flora-batch-generate.zip flora-batch-generate

Then upload it from Claude's settings, under skills/capabilities. Zipping from the repo rather than downloading a prebuilt archive means you always get the current version.

_Or just ask for it inline_ — see the raw-URL option below, which needs no setup at all and works in a normal chat.

Or no install at all — point your agent straight at one skill:

Read https://raw.githubusercontent.com/florafauna-ai/flora-mcp-skills/main/skills/flora-batch-generate/SKILL.md

and follow it for these 5 products:

PO-01 a matte black ceramic pour-over coffee dripper WB-04 a brushed steel insulated water bottle AP-09 a folded oatmeal linen apron CB-02 a walnut wood cutting board, rectangular SB-03 a stack of three speckled stoneware bowls

One consistent studio style across all five: seamless warm-grey backdrop, soft softbox from camera left, subtle contact shadow, 85mm, centred, no props.

Keeping the skills up to date

New skills get added to this repo, and existing ones get corrected as we measure things that turn out to be wrong. None of that reaches you on its own. An installed plugin is a frozen snapshot — it will not tell you a new skill exists, and it will keep working happily on an old copy. Updating is something you do, not something that happens.

Claude Code — two commands, no reinstall and no re-auth. Your MCP connection is untouched:

claude plugin marketplace update flora

claude plugin update flora-mcp-skills

The first refreshes this repo's marketplace listing; the second pulls the new version. Skipping the first means the second has nothing new to find. Changes apply on your next session — plugins load at start-up, so restart your agent afterwards.

If it reports already at the latest version, you are genuinely current. claude plugin list shows the version you are on.

Any other agent — re-copy. There is no update command, so pull the repo again and overwrite:

cd flora-mcp-skills && git pull

cp -r skills/* .codex/skills/ # Codex cp -r skills/* .cursor/rules/ # Cursor

Claude.ai — re-paste or re-zip. A Project's custom instructions and an uploaded Skill are both snapshots taken when you added them. Paste the current SKILL.md in again, or re-zip the folder from a freshly pulled clone and re-upload.

Raw URL — nothing to do. That path always serves main, so it is current the moment we push. If you want to be sure you are reading today's version of a skill, use it.

---

Start here: stop chatting, start batching

The single highest-leverage thing you can do with FLORA's MCP server is stop treating it as a chatbot and start treating it as a pipeline.

One request at a time, waiting for each, is the default an agent falls into and it is the slowest possible use of the server. FLORA runs generations concurrently. The serialisation is entirely on the agent's side.

Measured on a real six-item batch: fired together, 15.8 seconds. The same six run one after another: about 150 seconds. Identical cost, identical outputs, one tenth the wall clock — and the gap widens linearly with the size of your list.

**flora-batch-generate is the flagship skill

in this repo.** If you read one thing here, read that. It turns a product list, a set

of campaign variants, a folder of source images, or a spreadsheet into one parallel

batch, polls it correctly, and tells you exactly what failed and why.

---

Skills by use case

Scale — many items, one treatment

Refine — get one thing right, without burning money

Composite — animate what already exists

Sequence — script to moving pictures

Transform — you already have the image

| Skill