The one document that answers what a client actually owes you, aged as at any date you name, with the chaser drafted. It reads the three books this collection already keeps, the invoice ledger, the credit notes and the deposits, and turns them into a statement of account for a period: the balance carried at the start, every invoice issued, every payment received, every credit note given, the deposits applied broken out of the receipts rather than added on top of them, and the balance at the end. The movements come back in date order and the opening balance plus their sum is the closing balance, so the document reconciles line by line rather than only at the bottom. statement_aging splits what is still open into 0-30, 31-60, 61-90 and over 90 days past the due date AS AT the date you ask for, which means an invoice issued after that date is not on the books, a payment made after it has not happened, and a credit note issued after it has not been given. Due today is not overdue: day zero sits in a not-yet-due line reported beside the four buckets rather than hidden inside them. On the invoice the paid_minor field is the authority and the payment rows are only the attribution, so money that a deposit application put on an invoice without writing a payment row still appears, and when the two books disagree the difference is reported by name rather than scaled away. It writes into no book it reports on: the bytes and the mtimes of the sibling stores are unchanged across all six tools, and the only file it owns is a register of the statements it built. Nothing here invents a late fee, an interest rate or a legal cost, and a dunning letter escalates in tone and never in figures.
Eight tools against Cascade's ceiling of 100, and it pairs naturally with mcp-invoice, mcp-billing-docs and mcp-deposits, whose books it reads; budget the four at roughly 45 tools when you decide what else fits alongside them.
| You say | Tool |
|---|---|
| Send Acme Ltd a statement of account for June. What is the closing balance, and does it reconcile from the opening balance and the movements? | statement_build |
| Who owes me money right now, aged into 0-30, 31-60, 61-90 and over 90 days, per currency? | statement_aging |
| What was outstanding on 10 June, and how much of that was already overdue on that date? | statement_aging |
Aging a past date with today's payment figures does not go slightly wrong, it goes silently empty. Measured on this server's worked month at 2026-06-10: the as-at rule reports 2,500.00 outstanding of which 500.00 is 31 days late, while the ordinary rule almost every aging report is written as, subtract paid_minor and bucket by the due date, reports 1,700.00 outstanding and ZERO overdue, because a payment that arrived on 12 June has already been subtracted on the 10th. A third of the balance and all of the overdue disappear, the buckets still add up, and the answer cannot be reproduced next month because the input keeps moving. The dated subtraction is the step nobody writes a test for and the only one that decides who gets chased. A second measured figure from the same month: reconstructing receipts from the invoice payments[] rows alone would have lost 300.00 of 900.00 of cash, because deposit_apply raises paid_minor and writes no payment row, so paid_minor is treated as the authority and the rows only as the attribution.
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": {
"statement-of-account": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-statement-of-account"]
}
}
}Save and reopen the MCP Servers list; Cascade picks it up without restarting the editor.
The npm publish of @theluckystrike/mcp-statement-of-account is pending; until then use the .mcpb bundle or a clone and build from the latest release.
The same server runs at https://mcp.zovo.one/mcp/https://mcp.zovo.one/mcp/statement-of-account 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": {
"statement-of-account": {
"url": "https://mcp.zovo.one/mcp/https://mcp.zovo.one/mcp/statement-of-account",
"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: statement_aging is free and unlimited on every tier, for one client or for all of them: who owes me money is the question this server exists for, and a free tier that hides it is a demo rather than a tool. The meter is on the document that actually goes to a client, five distinct statements a calendar month, counted by client, period and currency, so rebuilding one already in the register is free forever. Plain-text statements and dunning letters at level 1 and level 2 are free. 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 Statement of Account contributes 8 tools, so keep the enabled list short rather than counting servers.
MCP Statement of Account in detail · The same server in VS Code and Cline · Every server in Windsurf · Guides · Windsurf docs · Buy Pro