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.
One config file for every workspace suits a tool you touch once a month: the schedules are reachable from whichever project happens to be open on the first.
| 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.
The file is mcp_config.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| macOS, Windows and Linux | ~/.codeium/windsurf/mcp_config.json |
If you also run Claude Desktop, the shortest path there is one click: recurring.mcpb
from the bundle catalog opens as an extension, with no JSON and no terminal.
Windsurf reads its own config, so here it is:
The config block:
{
"mcpServers": {
"recurring": {
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/recurring/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/recurring
That writes servers/recurring/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": {
"recurring": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-recurring"]
}
}
}
Save and reopen the MCP Servers list; Cascade picks it up without restarting the editor.
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/recurring 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": {
"recurring": {
"url": "https://mcp.zovo.one/mcp/recurring",
"headers": { "Authorization": "Bearer <token>" }
}
}
}
Read this first: mcp_config.json applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, takes its servers from the Devin CLI config files, so a correct entry here can still be invisible in a fresh tab. The other hard number is a cap: Cascade reaches at most 100 tools at once, and every enabled server spends from it.
Free: 3 active schedules, unlimited generation, a 30 day upcoming view and a 3 month forecast. Pro is $19 once, verified offline.
~/.codeium/windsurf/mcp_config.json, under mcpServers. Reach it from the MCPs icon at the top right of the Cascade panel, or Devin Settings, Cascade, MCP Servers.
That file applies to the legacy Cascade agent only. The Devin Local agent, the default for new tabs, reads its servers from the Devin CLI config files instead. Check which agent the tab runs.
Cascade reaches at most 100 tools at any one time, and every enabled server spends from that single budget. MCP Recurring Invoices contributes 13 tools, so keep the enabled list short rather than counting servers.
MCP Recurring Invoices in detail · The same server in VS Code and Cline · Every server in Windsurf · Guides · Windsurf docs · Buy Pro
Bill a retainer on a schedule without a billing SaaS · Create an invoice PDF from a chat message with an MCP server