McpStamp Invoices

Generate & send invoices from Claude with a free MCP server

Listed on the [AI Product Index](https://index.percall.dev/l/zovo-invoice.html) - live remote endpoint at mcp.zovo.one/s/invoice, free tier, no signup.

Featured on [Awesome MCP Servers](https://mcpservers.org) - directory listing | live hosted endpoint, free tier, no signup.

Say "make an invoice for Acme, 12 hours at 90 EUR, due in 14 days" and get a real PDF you can send. This MCP server stores your business profile and your clients, allocates a sequential invoice number that is never reused, computes the subtotal, any discount, one tax line per VAT rate and the total in integer minor units, and renders an A4 PDF with your issuer and payment details, a wrapping item table and a proper totals block. It also tracks payments and, on Pro, reports what is overdue and by how many days. Everything is stored in plain JSON files on your own machine; nothing is uploaded anywhere.

In the official MCP Registry (io.github.theluckystrike/invoice-pdf-billing-generator).

Create numbered invoices with tax lines and a real PDF from chat, no invoicing SaaS required.

60-second install

npm publish for @theluckystrike/mcp-invoice is pending. Until then, the .mcpb one-click bundle or a clone+build is the working path, both are verified below.

One-click (.mcpb): download invoice.mcpb from the latest release and double-click it in Claude Desktop: https://github.com/theluckystrike/mcp-servers/releases/latest

(claude_desktop_config.json):

{

"mcpServers": { "invoice": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-invoice"] } } }

Claude Code:

claude mcp add invoice -- npx -y @theluckystrike/mcp-invoice

(.cursor/mcp.json):

{

"mcpServers": { "invoice": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-invoice"] } } }

The npx form above starts working the moment the package is published. Until then, use the .mcpb bundle above, or build from source with exactly these three commands:

git clone https://github.com/theluckystrike/mcp-servers.git && cd mcp-servers

npm install npm run build -w packages/mcp-license -w servers/invoice

Then point your client's command at node with one arg: the absolute path to servers/invoice/dist/index.js.

To run in Pro mode set MCP_LICENSE_KEY in the same config block, or call license_activate once with your key.

Tools

Resource: invoices://open returns every unpaid or partly paid invoice as JSON.

Prompt: monthly_invoicing reviews what is unpaid and what is overdue for a month, then drafts the next invoice.

What you can say

Worked example

From docs/USER_VALUE_R2.md, the exact request tested end to end and independently checked against the arithmetic.

You: Invoice Acme for 12 hours of API work at 90 EUR plus a 300 EUR setup fee,

23% VAT, due in 14 days, and give me the PDF.

invoice_create { client: "Acme", currency: "EUR", due_days: 14, items: [ { description: "API work", quantity: 12, unit_price: 90, tax_rate: 23 }, { description: "Setup fee", quantity: 1, unit_price: 300, tax_rate: 23 } ] } -> INV-2026-0001, client "Acme" created with no address on file

invoice_pdf { number: "INV-2026-0001" } -> /Users/you/.../invoice/pdf/INV-2026-0001.pdf

Assistant: Created INV-2026-0001 for Acme. API work 12 h x EUR 90.00 = EUR 1080.00 Setup fee 1 x EUR 300.00 = EUR 300.00 Subtotal EUR 1380.00 Tax 23% on EUR 1380.00 EUR 317.40 Total EUR 1697.40 Note: Acme was created from a bare name with no address. Add one with client_add before you send this. PDF: INV-2026-0001.pdf

The arithmetic: 12 x 90 = 1080.00, plus 300.00 = 1380.00 subtotal; 23% of 1380.00 = 317.40; total 1697.40 EUR. Every amount on the PDF and in the text response carries its currency code, nothing is ever shown as a bare number.

Free vs Pro

Pro is a one-time $19, or $39 for every server in the collection, lifetime.

Numbers and money

Invoice numbers are PREFIX-YYYY-NNNN. The counter is persisted per prefix and year and is written before the invoice is stored, so a crash burns a number rather than reusing one; existing numbers are also scanned so a restored data file can never hand back a number that is already on a sent document.

Every money value printed anywhere - line unit prices, line amounts, subtotal, discount, each tax line, the total and the balance due, in the text response and on the PDF - carries its currency code, for example EUR 1080.00. No amount is ever shown as a bare number.

All amounts are held as integer minor units. How many make one unit comes from an ISO 4217 table, not a guess: 2 for most currencies, 0 for JPY, KRW, VND, CLP, ISK and the rest of the zero-decimal list, 3 for BHD, IQD, JOD, KWD, LYD, OMR and TND, 4 for CLF and UYW. KWD 1.234 is 1234 minor units, not 123. The table is identical to the one in mcp-expense-tracker, because the two servers exchange amounts and a currency that is 3-decimal in one and 2-decimal in the other would rescale money by ten. HUF is 2 decimals: ISO 4217 gives it two minor digits even though it is usually quoted without them. Rounding is per line, then summed: each line's gross is rounded first, an invoice-level discount_percent is applied and rounded per line, tax is computed and rounded per line and then grouped into one line per rate, and the totals are plain integer sums of those already-rounded values. A printed total can therefore never disagree with the printed lines. Dates are ISO YYYY-MM-DD.

How it stores data

Business profile, clients, invoices and the number counter live under ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/invoice/ as separate JSON files, plus a pdf/ subfolder holding the rendered PDFs. Every mutating call (business_set, client_add, invoice_create, invoice_from_hours, invoice_mark_paid) runs inside locked(), which takes an advisory lock file at .../invoice/.lock for the duration of the call, this is what makes number allocation safe when two invoices are created in the same second, since the counter read, increment and invoice write all happen under one lock. Saves go to a temporary file and are renamed into place. To back up your invoicing data, copy the whole invoice/ data directory, including pdf/ if you want the rendered files too, they can always be regenerated from the stored records with invoice_pdf.

If one of those JSON files is unreadable or not valid JSON, it is never treated as "empty". The file is moved aside byte-for-byte as .json.corrupt- , a .json.corrupt marker is written, and every tool returns data file is corrupt; moved to ...; nothing was written until you restore a good copy and delete the marker. A truncated clients.json can no longer be silently replaced by an empty client list.

Limits and honest caveats

• Free tier allows 3 invoices per calendar month; the counter resets on the 1st. overdue_report and everything else (clients, tax lines, discounts, payments, multi-currency) is unrestricted on free.
• Clients are never metered: the client list is unlimited on free and on Pro. client_add still refuses a record identical to a stored one, and client_delete removes an unused client, so a mistyped or duplicated record can always be undone without a licence key. A client any document references cannot be deleted.
• Free PDFs carry a small "Generated with mcp-invoice" footer line; Pro removes it and adds a logo.
• Creating an invoice for a client name the server has never seen creates that client with no address; the response says so and names client_add as the fix, but nothing blocks you from sending a PDF with a bare-name BILL TO block if you ignore the note.
• This server skips email-sending, payment-link and accounting-software sync: it produces the PDF and the record; getting it to the client is up to you.
• Currency conversion is not performed anywhere, an invoice's currency is fixed at creation and every line must use amounts already in that currency.

Troubleshooting

• `npx` hangs or fails to find the package: npm publish for this package is pending. Use the .mcpb bundle or the clone-and-build path above until it lands.
• **Using the