FLORA MCP

The FLORA MCP server lets any Model Context Protocol client — Claude, Cursor, VS Code, OpenAI Codex, Hermes Agent, OpenClaw, and others — discover and run your Techniques in plain English. No code, no API wiring. Connect once, then ask the agent to generate, iterate, branch, and batch using the same Techniques your team builds in FLORA.

Install

Claude CodeCursorVS CodeOpenAI CodexHermes AgentOpenClaw

What you can ask

Once FLORA MCP is connected, these prompts work in any MCP-compatible agent:

• “What FLORA Techniques would work for this campaign brief?” — the agent calls flora_list_techniques and returns Technique cards inline.
• “Run the Thumbnail v3 Technique with this brief and give me a 3×3 grid.” — the agent calls flora_run_technique and renders results inline as they finish.
• “Take #4 and #7 and make 10 more variations in the same direction.” — the agent re-runs the Technique with prior outputs as image references.
• “Now run those through the Social Motion Technique. I need 3-second loops for IG.” — the agent branches into another Technique, carrying the context forward.
• “Pull the localization sheet from Drive and run the Technique for all 12 markets.” — a coding agent loops over a spreadsheet and starts one run per market.

60-second quickstart

1. Install in your client

   Pick your client from the Install section above and follow the one-line setup.

2. Sign in with FLORA

   The first tool call triggers an OAuth flow. Sign in with the same account you use at app.flora.ai. Your client stores the token; you won’t be asked again until it expires.

3. Ask the agent to run something

   Try: “List my FLORA Techniques and pick one that generates product thumbnails.”

   The agent calls flora_list_techniques, shows the results, and asks which one to run.

How it works

FLORA MCP exposes flora_discover_skills and a set of flora_* endpoint tools to the agent:

• flora_discover_skills — lists reusable workflow skills when called without name, or returns instructions for an exact skill name.
• flora_* endpoint tools — expose the current FLORA API surface directly, including workspaces, projects, canvas, models, generations, techniques, actions, and assets.

Use the endpoint tools for direct API operations and flora_discover_skills when a larger reusable workflow needs discovery. Each endpoint tool wraps one public API call, so anything the agent does maps to an API Reference operation.

See the full tools reference for parameters and return shapes.

Why MCP, not just the API

The API is for engineers who want to ship integrations. MCP is for everyone else — designers, marketers, PMs, ops — who already work in an AI agent and want FLORA there too. Both surfaces hit the same Techniques and the same workspace billing.

	API	MCP
Audience	Engineers	Anyone using an AI agent
Setup	API key + code	Connect once via OAuth
Iteration	Programmatic	Conversational
Best for	Pipelines, batches, automation	Discovery, ideation, ad-hoc batches
Combine with	Webhooks, queues, your stack	Other MCP servers in the same chat (Drive, Slack, GitHub, …)

Next steps

• Install for your client — one page per supported tool.
• Recipes — concrete end-to-end scenarios.
• Tools reference — every tool, every parameter.
• Troubleshooting — OAuth, tool visibility, rate limits.