Put a CLI on npm for agents and document it

Ship a CLI an agent can run without a browser, with machine output and an exit code CI can read, using Ora, Stripe and Vercel as worked cases. 36 of 1,336 directory companies have a CLI package on record. First step: Make it runnable with npx and no account for read-only commands.

Steps

1. Make it runnable with npx and no account for read-only commands.
2. Offer --json output.
3. Fail with a non-zero exit code on a threshold.
4. Have the CLI configure your MCP server for detected agents.

What the sources say

• Ora's npx ax audit runs with zero install and no account; --json returns the full report; --min-score exits non-zero below the threshold. (ora.ai, read 4 November 2026)
• Stripe's stripe agent setup (from @stripe/cli) detects installed agents and configures the MCP server and skills. (docs.stripe.com, read 4 November 2026)
• Vercel's npx add-mcp https://mcp.vercel.com detects AI clients and configures each; -y skips confirmation and -g installs globally. (vercel.com, read 4 November 2026)
• Neon's npx neon@latest init sets up the MCP server, skills and a linked project. (neon.com, read 4 November 2026)
• AgentReady.org accepts a CLI in place of an MCP server for the act-layer MUST. (ora.ai, dated 19 October 2026, read 4 November 2026)

Case studies, asked the same questions

Ora's CLI is documented at ora.ai/docs/cli: npx ax audit yourdomain.com scores a domain, and the documented flags include --json for machine-readable output and --min-score for a pass or fail exit in CI. The npm record for ax was read separately from the directory run on 4 November 2026. Stripe's CLI is on npm as @stripe/cli (v1.55.8, published 3 November 2026, command stripe, read on 5 November 2026); its README also lists Homebrew, Scoop and a Docker image. A flag for machine-readable output was checked for Ora's CLI only (--json); Stripe's was not.

Every CLI on record