Three different products with the same word on the tin. einvoice-mcp builds and validates German XRechnung XML to EN 16931. IMW Invoice is a hosted service you connect over streamable HTTP that does invoicing, time tracking and billing behind an account. Ours produces a numbered A4 PDF from one sentence, on your own disk.
| Fact | Ours | einvoice-mcp | IMW Invoice |
|---|---|---|---|
| Tools | 10 plus license_status and license_activate | 4 | Not published in the registry entry |
| Transport | stdio, plus a hosted streamable HTTP endpoint | stdio (npm global install) | Hosted streamable HTTP only |
| Output | A4 PDF, plus CSV-ready invoice lines | XRechnung UBL 2.1 XML and CII extraction | Invoices in the hosted service |
| Account or API key needed | No | No, the README states no keys and no external services | Yes, a service account |
| Where invoices live | Local JSON and PDF files under your home directory | Files you pass in and out, local only | The provider's servers |
| Licence | MIT | MIT (npm record) | Not stated in the registry entry |
| Latest release read | 0.2.3 on the MCP registry | npm einvoice-mcp 0.1.5, 2026-04-13 | 1.4.0 on the MCP registry, 2026-09-01 |
| Compliance standards | Free text tax lines, several VAT rates per invoice | EN 16931, XRechnung 3.0.2, BR-DE rules | Not stated in the registry entry |
Pick it if you invoice German public bodies, or German business customers after the deadlines its README lists. Its four tools create XRechnung UBL 2.1 XML, validate an invoice against syntax, mandatory fields and German BR-DE business rules, extract structured data out of UBL or CII XML, and look up format information. We produce a PDF, which is a different artefact: a PDF is not a valid e-invoice under that regime. If a customer asks for XRechnung or ZUGFeRD, use that server, or use both and generate the PDF for your own records.
Pick it if you want invoicing, time tracking and billing in one hosted place and are comfortable with an account. It is a remote server, so there is nothing to install on any machine and it works from a phone client. Its registry entry publishes a streamable HTTP endpoint and no repository, so the tool list, licence and pricing are not verifiable from public metadata; read the provider's own site before committing.
Pick ours when you send ordinary PDF invoices and want them created where you already work. Say the
invoice in a sentence and the server allocates the number, computes the tax lines and renders A4.
Numbers follow INV-YYYY-NNNN and are never reused even after a delete, because a gap in the sequence is
what a tax authority asks about. Allocation happens under a file lock, so two invoices created in the
same second do not collide. Amounts are integer minor units, rounded per line before summing, so the
printed total equals the printed lines added up. invoice_from_hours takes the output of
the time tracker directly, and overdue_report lists what is
unpaid past its due date. Nothing leaves the machine, which matters for a client under NDA.
The invoice package carries 23 automated tests, all passing, covering money arithmetic, rounding, the stdio protocol and two concurrent number allocations. The validate.mjs probe suite is at 121 of 121. In user value round 5 the invoice scenario was driven through the real Claude CLI and scored 1 of 3, the weakest result in the suite: the model produced the invoice but the run exposed defects in the unbilled-work path. That is the honest number, it is published in our own docs, and it is the reason this server is the current work item rather than a finished one. An earlier audit verified the arithmetic end to end: 12 hours at 90 EUR plus a 300 EUR setup fee at 23 percent VAT produced 1,697.40 EUR from a plain sentence.
Ours, Claude Code:
claude mcp add invoice -- npx -y @theluckystrike/mcp-invoiceeinvoice-mcp:
npm install -g einvoice-mcp
claude mcp add einvoice -- einvoice-mcpIMW Invoice:
claude mcp add --transport http imw-invoice https://invoice.independent.management/mcpPer client config paths are on the setup pages, the product page is MCP Invoice, and the invoice guide walks through a full example.
No. It renders a PDF and stores invoice data as JSON. For EN 16931 formats use einvoice-mcp, which is built for exactly that and needs no account.
Numbers are allocated as INV-YYYY-NNNN under a file lock and are never reused, including after a delete, so the sequence has no reused values. Whether the rest satisfies your jurisdiction is between you and your accountant.
Because the alternative is a claim we cannot support. Round 5 drove ten fresh scenarios through the real Claude CLI and scored 26 of 30 overall; the invoice scenario scored 1 of 3 and the defects are listed in our repository docs.
No. Rendering is local with pdfkit and the server makes no network calls, so an invoice for a client under NDA never leaves the machine.
Three invoices a month with a small footer line, and the overdue report is included. Pro at $19 once removes the limit and the footer and adds a logo and a custom number prefix.