flo-plugin
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLO_OAUTH_CLIENT_ID | Yes | Your OAuth client ID from floapp.co/settings/api |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| flo_auth_loginA | Start OAuth login (browser PKCE flow), cache token locally, and return auth status. If prompted by hosted login UI, first sign in via appLoginUrl. |
| flo_auth_statusA | Show current auth mode and cached OAuth token status. |
| flo_auth_setup_helpA | Show where to find/configure FLO_OAUTH_CLIENT_ID and expected Cognito app client details. |
| flo_auth_logoutA | Clear cached OAuth token from local disk. |
| flo_analyzeC | Analyze an asset directly (friendly alias for /flo:analyze-image ). |
| flo_searchC | Run /flo:search against interface-agent and return plugin menu items. |
| flo_queryA | Run /flo:query against interface-agent and return filename-first candidates plus follow-up commands. |
| flo_skill_routingB | List available actions for an asset (what can I do with this file?). |
| flo_qc_logoC | Run /flo:qc-logo using stored-image reference mode for the Claude plugin happy path. |
| flo_commandC | Run a raw /flo:* slash command against interface-agent for troubleshooting. |
| flo_plugin_healthcheckA | Check config/auth/runtime reachability for the Flo Claude Co-Work plugin. |
| flo_happy_path_runA | Run search -> skill routing -> qc logo in one tool call for end-to-end validation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools have distinct purposes (auth vs. core operations), but flo_happy_path_run overlaps with the individual search/skill routing/qc_logo tools, and flo_query vs. flo_search could be confused despite different return types.
All tools start with 'flo_' but the naming pattern is inconsistent: some are verbs (analyze, query, search), some are nouns (command, status), and others are compound phrases (auth_login, happy_path_run).
12 tools is reasonable for a plugin that covers authentication, search, analysis, and troubleshooting. Not overly numerous nor too few for the apparent scope.
The tool set covers the main workflow (search -> skill routing -> analyze -> QC) plus auth and health check. Missing explicit asset listing but can be inferred from search results.