Numbered invoices with tax lines, rendered to a PDF. It stores your business profile and clients, allocates numbers that never repeat, computes per-line rounding and several VAT rates in integer minor units, and renders an A4 PDF.
If you invoice per repository, .cursor/mcp.json inside the client project keeps that client's invoice server scoped to that project, which is the cleanest separation any of the six clients here offers.
| You say | Tool |
|---|---|
| Invoice Acme for 12 hours at 90 EUR plus 300 EUR setup, 23% VAT, PDF. | invoice_create then invoice_pdf |
| Which invoices are unpaid and overdue? | overdue_report |
| Mark INV-2026-0007 as paid in full. | invoice_mark_paid |
In the audit run this issued INV-2026-0001: subtotal EUR 275.00, 23% VAT EUR 63.25, total EUR 338.25. The file on disk began with %PDF-1.3 at 2,495 bytes.
The file is .cursor/mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| This project only | <project>/.cursor/mcp.json |
| Every project | ~/.cursor/mcp.json |
If you also run Claude Desktop, the shortest path there is one click: invoice.mcpb
from the bundle catalog opens as an extension, with no JSON and no terminal.
Cursor reads its own config, so here it is:
The config block:
{
"mcpServers": {
"invoice": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/invoice/dist/index.js"]
}
}
}The node command above wants a built file. From a clone, once:
git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/invoiceThat writes servers/invoice/dist/index.js, and its absolute path is the one argument
the config needs.
The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:
{
"mcpServers": {
"invoice": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-invoice"]
}
}
}The Customize page shows the server and its tools once it has started.
Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the bundle catalog, a clone and build, or the hosted URL.
The same server runs at https://mcp.zovo.one/mcp/invoice over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.
{
"mcpServers": {
"invoice": {
"url": "https://mcp.zovo.one/mcp/invoice",
"headers": { "Authorization": "Bearer <token>" }
}
}
}The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.
Free: 3 invoices a month with a small footer line, overdue report included. Pro is $19 once, verified offline.
<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.
The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.
Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Invoice pasting the config block above is the supported route.
MCP Invoice in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs · Buy Pro
Create an invoice PDF from a chat message with an MCP server · Freelancer invoicing from chat: billable hours to invoice lines to PDF without a SaaS subscription · Send a quote from chat, then turn the yes into an invoice · Bill a retainer on a schedule without a billing SaaS · Turn a quote or estimate into an invoice without retyping it