FLORA MCP

The FLORA MCP server lets any Model Context Protocol client — Claude, Cursor, VS Code, Windsurf, Zed, 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.

Server URL: https://florafauna-ai.stlmcp.com/
Transport: Streamable HTTP
Auth: OAuth (your FLORA account)

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 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 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 batches the calls.

60-second quickstart

1. Install in your client

   Pick your client and run the one-line install:

   • Claude Code: claude mcp add --transport http flora https://florafauna-ai.stlmcp.com/
   • Claude.ai / Claude Desktop: Settings → Connectors → Add custom connector → paste the URL
   • Cursor: Add to ~/.cursor/mcp.json
   • VS Code: code --add-mcp '{"name":"flora","type":"http","url":"https://florafauna-ai.stlmcp.com/"}'

   Full instructions for every supported client.

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 will call list_techniques, show the results, and ask which one to run.

How it works

FLORA MCP wraps the same REST API your developers use. Every API operation is exposed as a tool the agent can call:

Resource	Tools
Techniques	list_techniques, retrieve_technique, create_technique_run, retrieve_technique_run
Runs	start_technique_run, start_generation_run
Assets	create_asset, complete_asset, retry_asset, list_assets, retrieve_asset
Projects	list_projects, create_project, retrieve_project, list_project_nodes, attach_project_asset
Workspaces	list_workspaces
Models	list_models
Feedback	record_feedback

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 credits.

	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.