Home · Setup · Claude Code

MCP Billing Docs in Claude Code

Credit notes and purchase orders written against the invoices the invoice server already holds, with the VAT unwound at the rate you charged. It credits an invoice in full, by a gross amount or by named lines and quantities, storing every money field negative in minor units so a period's documents sum to the net of what was billed, and it refuses to give back more than the invoice's remaining creditable amount. It also raises purchase orders to suppliers with line items, VAT, currency and an expected delivery date, receives them in full or in part, and reports credited and on-order totals per currency alongside deliveries past their date.

Both servers read one XDG data directory per machine, so `claude mcp add billing-docs` alongside `claude mcp add invoice` at any scope sees the same invoices and the same client list, and the 5-document monthly allowance is counted once for the box rather than once per project.

What you get in Claude Code

You say	Tool
Credit invoice INV-2026-0001 in full, the client sent the work back.	`credit_note_create`
Raise a purchase order to Nordic Print for 500 brochures at 1.20 each, due the 20th.	`purchase_order_create`
Which purchase orders are past their delivery date?	`billing_docs_report`

Crediting ten percent of a mixed-VAT invoice at a single rate and splitting it across the invoice's own rates give the same gross, EUR 177.00, and VAT lines that differ by EUR 6.10, 22.6 percent. The client's document and the payment are identical either way, so nothing downstream ever surfaces the error; only the VAT return does. The split is done at the point the document is written.

Install it in Claude Code

The file is .mcp.json, and the key inside it is mcpServers.

Scope	Path
local (default)	`~/.claude.json, this project only`
project	`.mcp.json at the repository root`
user	`~/.claude.json, every project`

If you also run Claude Desktop, the shortest path there is one click: billing-docs.mcpb from the bundle catalog opens as an extension, with no JSON and no terminal. Claude Code reads its own config, so here it is:

From the terminal, against a built file:

claude mcp add --scope user billing-docs -- node /absolute/path/to/mcp-servers/servers/billing-docs/dist/index.js
claude mcp list    # health-check it before the first prompt

# or --scope project, committed to .mcp.json for the team

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/billing-docs

That writes servers/billing-docs/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:

claude mcp add billing-docs -- npx -y @theluckystrike/mcp-billing-docs

No restart. The entry is picked up in the next session, and `/mcp` reconnects one on demand.

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.

No install: the hosted endpoint

The same server runs at https://mcp.zovo.one/mcp/billing-docs 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.

claude mcp add --transport http billing-docs https://mcp.zovo.one/mcp/billing-docs \
  --header "Authorization: Bearer <token>"

Claude Code notes worth knowing first

The `--` is load-bearing: it separates Claude Code's own options, such as --transport, --env and --scope, from the command that runs the server. And the default scope is local, private to you and to the directory you ran it in, so adding it in the wrong folder leaves the tools absent with no error at all.

Free: 5 documents a calendar month, credit notes and purchase orders together, counted by issue date. Both text exports are never metered, and full, partial and per-line credit notes, VAT, multiple currencies and receiving orders are all on the free tier. Pro is $19 once, verified offline.

Questions

Which scope should I use for MCP Billing Docs?

Local, the default, writes ~/.claude.json and is private to you and that directory. --scope project writes .mcp.json at the repository root, shared through version control. --scope user loads it everywhere.

Why did my first prompt ignore the server?

Measured, not documented: of three fresh projects, one first prompt made zero tool calls although initialize answered in 1.05 seconds. Run claude mcp list once first: it prints Connected, and the next run used the tool.

Can I use MCP Billing Docs without installing anything?

Yes: claude mcp add --transport http billing-docs https://mcp.zovo.one/mcp/billing-docs --header "Authorization: Bearer <token>". Mint a free token at https://mcp.zovo.one/mcp/token or use a Pro key. -t and -H are the short forms.

MCP Billing Docs in detail · The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs · Buy Pro

Related guides & tools

Credit notes and purchase orders from chat, against your real invoices · Fixed assets and depreciation from chat, on the rates the tax authorities publish