Home · Setup · Claude Code

MCP Recurring Invoices in Claude Code

Retainers and subscriptions billed on a schedule you set once. It stores a billing schedule per client, weekly, monthly, quarterly, yearly or every N days, shows what falls due, and generates exactly one invoice per schedule per period into the invoice server's own store with its number series and its A4 PDF.

The whole month closes in one session: run the schedules, then invoice the ad hoc hours out of the time tracker into the same invoice store, then read overdue_report. All three servers write to the same directory.

What you get in Claude Code

You say	Tool
Bill Acme 12 hours at 90 EUR every month from the 1st, 14 day terms.	`schedule_create`
Show me what this month's billing run would create before you create it.	`invoice_generate_due with dry_run`
What is due in the next 30 days?	`schedule_upcoming`

The worked run created 4 invoices totalling EUR 4,320.00 and, repeated five minutes later, created 0 and skipped 4. The key is the period, not the calendar day, so a billing run you forgot you already did is a no-op rather than four duplicate invoices.

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`

claude mcp add recurring -- npx -y @theluckystrike/mcp-recurring
claude mcp list    # health-check it before the first prompt

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

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

The npm publish of @theluckystrike/mcp-recurring is pending; until then use the .mcpb bundle or a clone and build from the latest release.

No install: the hosted endpoint

There is no hosted endpoint for this one yet. MCP Recurring Invoices runs locally over stdio with the config above, which is also the only form in which it reads and writes files on your own disk. Three of the servers in this collection are served at https://mcp.zovo.one/mcp/<name> over MCP streamable HTTP: time-tracker, price-tracker and invoice.

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: 3 active schedules, unlimited generation, a 30 day upcoming view and a 3 month forecast. Pro is $19 once, verified offline.

Questions

Which scope should I use for MCP Recurring Invoices?

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 Recurring Invoices without installing anything?

Not yet. MCP Recurring Invoices runs locally over stdio, which is also how it reads and writes files on your disk. The hosted endpoints at https://mcp.zovo.one/mcp currently cover time-tracker, price-tracker and invoice.

MCP Recurring Invoices in detail · The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs