@fload-ai/cli
v0.1.1
Published
Fload from a terminal: every tool Fload's MCP server offers, as commands. Mobile app analytics, reviews, ASO, ads and approvals.
Maintainers
Readme
@fload-ai/cli
Fload from a terminal (FLO-3682). Every tool Fload's MCP server offers your API key is a command, with the same scopes, rate limit and approvals your AI client gets. Writes stage an inbox card for a person to approve; nothing reaches a store from here.
Install it with npm install -g @fload-ai/cli (Node.js 20 or later). It puts
the fload command on your path.
fload login # paste a key from Settings > API keys
fload whoami # the server, the key, what it can do
fload use "Pocket Budget" # the app commands use without --app
fload help # every command
fload apps
fload reviews --app "Pocket Budget" --rating 1
fload reviews reply <review-id> "Thanks, a fix ships Friday." --app pocket
fload approvals --app pocket # every command about an app takes --app
fload approvals approve <action-id> # asks first; --yes in a script
fload reports export <report-id> --app pocket > audit.md
fload tool list # every tool this key is offered
fload tool getReviews --help # a tool's flags, from its schema
fload tool getReviews --asset-id <id> --limit 20
fload tool listAssets --json # the answer exactly as MCP returns itFload's MCP keeps every list to one app, so every command about an app needs
one: --app (a name, bundle id or id), else the app fload use saved, else
the organization's only app. The fload use app belongs to the saved key, so
a run on FLOAD_API_KEY (perhaps another organization's) leaves it out.
The key
fload login reads the key without showing it (from stdin in a pipe:
echo "$KEY" | fload login), checks it with one tools/list, and saves it in
~/.fload/config.json for its owner only (0600). That is the file
@fload-ai/mcp reads, so one login serves both. FLOAD_API_KEY wins over
the file, for scripts and CI, on the server FLOAD_API_URL names; a saved key
keeps the server it was saved with, as in @fload-ai/mcp (one written by hand
without apiUrl is for Fload's own, never FLOAD_API_URL). fload login
--api-url <url> signs in to another Fload; fload logout forgets the key
(revoke it in Settings > API keys).
A staged card prints its inbox link (https://platform.fload.com/inbox?asset=...&request=...)
and fload approvals approve <id>. For a server other than Fload's own, set
FLOAD_APP_URL to its web app to get the link.
How it stays in step with the MCP
The CLI holds no tool code. It is an MCP client of the same /mcp endpoint
@fload-ai/mcp relays to, and builds each tool's flags from the JSON schema
in tools/list, so a tool added to the server is a command the same day.
test/tool-manifest.jsonis what a key with every scope lists. apps/api'sintegration/oauth/mcp-tool-manifest.test.tsfails when it is stale and rewrites it withFLOAD_WRITE_TOOL_MANIFEST=1 pnpm --filter api test:integration --run oauth/mcp-tool-manifest.test/manifest-parity.test.tsruns every manifest tool through its flags.test/curated-parity.test.tsholds each curated command (src/commands.ts, one tool each) to a tool and arguments in the manifest, and puts every manifest tool in a noun's help by its scope's area.
Exit codes
| Code | Meaning |
| ---- | ---------------------------------------------- |
| 0 | ok (a staged card is ok) |
| 1 | the tool refused or failed |
| 2 | bad command, flag or value; tool not offered |
| 3 | no key, or Fload refused it (401) |
| 4 | the key lacks the scope |
| 5 | the app (--app or fload use) was not found |
| 6 | rate limited (120 calls a minute per key) |
| 7 | Fload unreachable |
