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.
The deposit and the invoice it settles are usually decided in the same chat as the work, so deposit_apply closes the loop without leaving the editor, and deposit_statement_text gives you the message to send the client without a second tool.
| 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 .cursor/mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| This project only | <project>/.cursor/mcp.json |
| Every project | ~/.cursor/mcp.json |
{
"mcpServers": {
"deposits": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-deposits"]
}
}
}The Customize page shows the server and its tools once it has started.
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.
The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.
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.
<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.
The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.
Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Deposits pasting the config block above is the supported route.
MCP Deposits in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs · Buy Pro