flo-plugin
OfficialThis server provides AI-powered media automation for the Flo platform, enabling asset management, quality control, and media analysis through Claude.
Authentication: Manage OAuth tokens — initiate login (
flo_auth_login), check status (flo_auth_status), log out (flo_auth_logout), and get client ID setup help (flo_auth_setup_help).Asset Search & Discovery: Search the Flo library by query (
flo_search) or perform filename-first lookups (flo_query).Asset Analysis & Skill Routing: Analyze a media asset by ID (
flo_analyze) and list available actions for a given asset (flo_skill_routing).Quality Control: Run logo QC by comparing an asset against a reference image, with optional PDF output (
flo_qc_logo).Health & Validation: Check auth, config, and connectivity (
flo_plugin_healthcheck), or run a full end-to-end validation — search → skill routing → logo QC — in one call (flo_happy_path_run).Raw Command Execution: Execute arbitrary
/flo:*slash commands for advanced debugging (flo_command).Token Override: Most tools accept an optional
authTokenparameter to override the cached token per call.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@flo-pluginQC the latest promo video for logo consistency"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Flo Plugin for Claude
The official Flomenco plugin for Claude. Brings Flo's AI-powered media automation into Claude Code via slash commands, and connects Claude Desktop to the Flo platform via MCP.
Do not use npx @flomenco/claude-plugin-mcp in Claude Code — npm is stuck
at 0.2.2 without AgentCore SSE parsing, so flo_happy_path_run fails while
individual tools appear to work. Use marketplace install (or node scripts/run-mcp.js
from this repo).
Quick start (Claude Code)
1. Install the plugin
In Claude Code:
/plugin marketplace add Flomenco-Inc/flo-plugin
/plugin install flo-plugin@flo-plugins
/reload-plugins2. Authenticate
Ask Claude to run flo_auth_login — it opens a browser window, completes the
OAuth flow, and caches your token locally. You only need to do this once (or
when your token expires).
Production: the plugin ships prod defaults in .mcp.json. Copy your OAuth
client ID from floapp.co/settings/api (Claude
Plugin tab) into the plugin MCP env only if flo_auth_login reports a missing
client ID.
Dev / staging: marketplace .mcp.json ships prod defaults. Override using
any of:
~/.flo/claude-plugin-mcp.env— copy the env block from Settings → API → Claude Plugin (recommended).Legacy
~/.claude.json— if you already havemcpServers.flo-plugin.envfor a manual MCP server, the plugin MCP merges those vars automatically.Claude Code plugin MCP env UI for
plugin:flo-plugin:flo-plugin.
Run npm run sync-versions before release so marketplace.json matches
package.json (required for /plugin marketplace update to pull new builds).
3. Validate
flo_plugin_healthcheck
flo_happy_path_runWindows, macOS, and Linux
The MCP server starts via node scripts/run-mcp.js (see .mcp.json). You
need Node.js ≥ 22.13 and npm on your PATH. No Bash or WSL required.
Config and tokens live under
%USERPROFILE%\.flo\on Windows and~/.flo/on Unix.OAuth login opens your default browser (
cmd /c starton Windows).Optional env overrides:
%USERPROFILE%\.flo\claude-plugin-mcp.env(Windows) or~/.flo/claude-plugin-mcp.env(macOS/Linux).
Related MCP server: facets-control-plane-mcp-server
Commands
Command | Description |
| Search for assets in your Flo library |
| Filename-first asset lookup |
| List available actions for an asset |
| Logo QC against a stored reference image |
| QC workflow picker (logo vs moderation) |
| Content moderation against a target rating and platform |
| Validate a media asset against platform delivery specs |
| Analyze a media asset directly |
| Show current auth and config status |
MCP tools
Tool | Description |
| Start OAuth login (browser PKCE flow) |
| Show current auth state and token info |
| Clear cached token |
| Show where to find your client ID |
| Search the Flo asset library |
| Filename-first asset lookup |
| Analyze a media asset |
| Run logo QC against a reference asset |
| List available actions for an asset |
| Check auth and connectivity |
| End-to-end validation in one call |
| Run a raw |
Claude Desktop installation
Run the install script (requires AWS credentials with Cognito read access):
npx @flomenco/claude-plugin-mcp install:claude-desktopOr clone the repo and run:
node tools/install-claude-desktop.jsThen fully quit and relaunch Claude Desktop.
Troubleshooting
flo_auth_login fails with "Invalid URL" or missing client ID
Open floapp.co/settings/api, copy the OAuth
client ID from the Claude Plugin tab, and set FLO_OAUTH_CLIENT_ID in your MCP
env block. For dev, copy the full env block from that page.
flo_plugin_healthcheck returns unreachable
Check that you have network access to plugin.floapp.co. If you're on a VPN,
try disconnecting.
Commands not appearing after install
Restart Claude Code, or run /reload-plugins.
Token expired
Ask Claude to run flo_auth_logout followed by flo_auth_login.
Contributing
See CONTRIBUTING.md for how to add new tools or commands.
License
MIT — see LICENSE.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Flomenco-Inc/flo-plugin'
If you have feedback or need assistance with the MCP directory API, please join our Discord server