Security and retainer deposits held per client, applied to the invoices the invoice server already holds. It records a deposit when the money arrives, in minor units and in the currency it arrived in, then answers for it: what is held per client and per currency, since when, and what has already gone. Applying a deposit to an invoice writes the payment onto that invoice under both locks, adding to what was already paid rather than replacing it, and it can never pay out more than the deposit still holds or more than the invoice still owes. Refunds hand the money back without touching the invoice, and the statement is one client in one currency, as text or as an A4 PDF that matches the invoice and credit note beside it.
Ten tools against Cascade's ceiling of 100, and this one is only useful with mcp-invoice enabled beside it, so budget the pair at roughly 26 tools when you decide what else fits.
| You say | Tool |
|---|---|
| Record a 500 euro security deposit from Nordic Print, received today. | deposit_record |
| Apply 300 of that deposit to INV-2026-0001. | deposit_apply |
| How much are we holding for Nordic Print, and since when? | deposit_balance |
deposit_apply ADDS to the invoice's amount paid rather than setting it. Measured through a real client on 2026-09-05: an invoice already carrying a EUR 200.00 bank transfer ended at paid_minor 50000 after a EUR 300.00 deposit was applied, reported as paid EUR 500.00 of EUR 1,230.00 with EUR 730.00 due. Writing this server against the same field is what surfaced that invoice_mark_paid was assigning rather than adding, which silently lost the earlier payment; the invoice server was fixed the same day and now adds too.
The file is mcp_config.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| macOS, Windows and Linux | ~/.codeium/windsurf/mcp_config.json |
{
"mcpServers": {
"deposits": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-deposits"]
}
}
}Save and reopen the MCP Servers list; Cascade picks it up without restarting the editor.
The npm publish of @theluckystrike/mcp-deposits is pending; until then use the .mcpb bundle or a clone and build from the latest release.
There is no hosted endpoint for this one yet. MCP Deposits 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.
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: 5 deposits recorded a calendar month, counted by received date. Applying to invoices, refunds, lists, balances and the text statement are unlimited on every tier: a cap that trapped a client's deposit would be a limit on their money rather than on yours. 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 Deposits contributes 10 tools, so keep the enabled list short rather than counting servers.
MCP Deposits in detail · The same server in VS Code and Cline · Every server in Windsurf · Guides · Windsurf docs · Buy Pro