storno-cli vs InvoiceFlow
storno-cli is an MCP server published by stornoro. Marketplaces we read that list it: 1 (npm registry (MCP servers)). InvoiceFlow is an MCP server published by EarthyPunyapat. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  storno-cli |  InvoiceFlow |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 1.0.57 Downloads/month (npm): 1 668 Downloads/week (npm): 801 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | storno-cli | InvoiceFlow |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-28 | Not published |
| Where it runs (differs) | On your machine (storno-cli) | Remote server (invoiceflow-ten-azure.vercel.app/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Elastic-2.0 | Not stated |
| Repository (differs) | github.com/stornoro/storno-cli | github.com/earthypunyapat/invoiceflow |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-12 | 2026-11-02 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 45 h ago returned HTTP 405 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
storno-cli
MCP server for the Storno.ro e-invoicing API — enables AI tools (Claude, Cursor, Windsurf) to manage invoices, clients, companies, and the full e-Factura workflow
InvoiceFlow
Create invoices, clients, and Stripe payment links from any agent. 7 tools. No email or deletes.
How to run each
storno-cli
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
InvoiceFlow As a remote MCP server
claude mcp add --transport http invoiceflow https://invoiceflow-ten-azure.vercel.app/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only InvoiceFlow has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: storno-cli · What it can do: InvoiceFlow · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.