Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Description from the maker (original English)
Generate and edit images, video, audio, text and 3D on FLORA's AI creative canvas.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://agents.flora.ai/mcpRun this in your terminal
claude mcp add --transport http flora https://agents.flora.ai/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"flora": {
"url": "https://agents.flora.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"flora": {
"type": "http",
"url": "https://agents.flora.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://agents.flora.ai/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain flora.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.11.5) reached the registry 20 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Let any LLM watch a video locally — and search everything it has ever watched.
Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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:
https://agents.flora.ai/mcpChatGPT — FLORA is in the app directory; enable it there.
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.
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.
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-generateis 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.
| Skill | Use it when |
|---|---|
| [flora-batch-generate](skills/flora-batch-generate/SKILL.md) ★ | You have a list — products, SKUs, campaign variants, localisations, scenes — and want one asset per row under a single consistent style. Handles parallel firing, batch polling, per-item variables, partial failure and retry classification. Start here. |
| Skill | Use it when |
|---|---|
| [flora-refine-loop](skills/flora-refine-loop/SKILL.md) ★ | The first result is wrong and you need to drive it to a specific goal — "that's not quite right", "closer, but the X is off". Uses a free vision judge to name the defect, changes the prompt to fix it, and stops when the goal is met or the defect stops moving. Reach for this the moment someone is re-running the same prompt hoping for a better roll. |
| Skill | Use it when |
|---|---|
| [flora-motion-compositor](skills/flora-motion-compositor/SKILL.md) | The subject already exists — a UI screenshot, a logo, a product photo, a Figma export — and you need real motion-graphics shots of it: 3D-tilted screens, staggered type reveals, camera moves, grade. Nothing is generated; every pixel comes from a file or a font, so type is pin-sharp, spelling is correct, and two renders of a scene are byte-identical. Renders from a JSON scene graph at $0 and ~12s a shot, which makes re-rendering a whole film after a design change free. |
| Skill | Use it when |
|---|---|
| [flora-script-to-video](skills/flora-script-to-video/SKILL.md) | You have a script or narrative and want animated clips. Staged pipeline with approval gates — script → shot list → consistent keyframes → motion — because a clip costs 30–90x its keyframe, so a drifted still must be caught before it is animated. Delivers ordered clip URLs, not a finished cut. |
| Skill
Only the beginning is shown; read the rest in the repo