Home · Setup · Windsurf

MCP Recurring Invoices in Windsurf

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.

What you get in Windsurf

You sayTool
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 Windsurf

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

ScopePath
macOS, Windows and Linux~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "recurring": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-recurring"]
    }
  }
}

Save and reopen the MCP Servers list; Cascade picks it up without restarting the editor.

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.

Windsurf notes worth knowing first

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.

Questions

Where does Windsurf keep its MCP config?

~/.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.

I edited the file and a new tab still cannot see MCP Recurring Invoices.

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.

How many servers can I load at once?

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.

Related

MCP Recurring Invoices in detail · The same server in VS Code and Cline · Every server in Windsurf · Guides · Windsurf docs