freee-mcp vs InvoiceFlow
freee-mcp is a plugin bundle for AI coding tools published by freee. Marketplaces we read that list it: 2 (Community GitHub marketplaces, 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 |   freee-mcp |  InvoiceFlow |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 0.37.11 Downloads/month (npm): 48 149 Downloads/week (npm): 19 432 Forks (GitHub): 57 Stars (GitHub): 515 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 | freee-mcp | InvoiceFlow |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 515 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 57 (better) | 0 (worse) |
| Last release (differs) | 2026-11-05 | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (invoiceflow-ten-azure.vercel.app/api/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/freee/freee-mcp | github.com/earthypunyapat/invoiceflow |
| Changes in the last 7 days (differs) | 4 | 2 |
| First seen (differs) | 2026-10-12 | 2026-11-02 |
| Endpoint at the last check (differs) | Status out of date: last check 42 h ago returned HTTP 401 | 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
freee-mcp
freee API を MCP 経由で操作するためのスキル。詳細なAPIリファレンス（パラメータ、リクエストボディ、レスポンス情報含む）と、freee-mcp を使用した API 呼び出しガイドを提供。OAuth 認証とトークン管理を自動化し、経費申請、会計データ取得、人事情報管理など、freee の様々な機能を利用可能。
InvoiceFlow
Create invoices, clients, and Stripe payment links from any agent. 7 tools. No email or deletes.
How to run each
freee-mcp As a Claude Code plugin
/plugin marketplace add freee/freee-mcp
/plugin install freee-mcp@freee-mcp-marketplaceInvoiceFlow 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.
Both endpoints responded at the last daily 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: freee-mcp · What it can do: InvoiceFlow · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.