npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

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

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 it

Fload'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.json is what a key with every scope lists. apps/api's integration/oauth/mcp-tool-manifest.test.ts fails when it is stale and rewrites it with FLOAD_WRITE_TOOL_MANIFEST=1 pnpm --filter api test:integration --run oauth/mcp-tool-manifest.
  • test/manifest-parity.test.ts runs every manifest tool through its flags.
  • test/curated-parity.test.ts holds 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 |