Chase unpaid invoices: reminder, firm reminder and final notice letters, and a daily chase list.
Scored across 11 tools
Each tool has a distinct role: register/status/delete operate on a single invoice, letter_render vs letter_sent separate production from recording, and payment/license tools are clearly separate. The three reporting views (aging_summary, overdue_list, chase_today) overlap the most, but their descriptions sharply distinguish aggregate aging, past-due ranking, and today's escalation actions.
There is a recognizable noun-prefix grouping (invoice_*, letter_*, license_*) but the second element is inconsistent: imperatives (register, delete, render, activate, record) mixed with non-verbs (status, sent, summary). Three tools (aging_summary, chase_today, overdue_list) sit outside any prefix group, so the pattern is readable but not predictable.
Eleven tools is well within a comfortable range for a dunning-letters workflow, and each earns its place: four lifecycle operations, three reporting views, two letter-ladder steps, and two licensing tools.
The core lifecycle is covered end to end: register, view, list/aggregate, render, record sending, record payment, delete. The notable gaps are the absence of any update/edit operation (correcting an amount or due date requires delete-and-re-register) and no way to close, pause, or manually advance the ladder for invoices stuck after the final notice.
The aging summary across every unpaid invoice: current, 1-30, 31-60, 61-90 and 91+ day buckets, with counts and totals in integer cents, per currency. This is the answer to "how much am I owed, and how stale is it".
Inputs: on.
The day's chase list: which invoices cross an escalation threshold today, which letter to send each and how long it has been waiting, what falls due in the next few days, and which invoices have had all three letters and need a decision outside this server.
Inputs: on, within_days.
Delete an invoice entered wrongly, by id or reference: the record, its payments and its letter history. The id is not reissued, so a gap in the DUN series is the record that a deletion happened.
Inputs: invoice (required).
Start chasing an unpaid invoice: register the client, the invoice reference, the amount in integer cents, the currency and the due date, and get the three-letter escalation schedule (reminder 1, reminder 2, final notice) with the date each falls due. Free tier: 3 unpaid invoices chased at once.
Inputs: due (required), client (required), currency (required), reference (required), +6 more.
One chased invoice in full: what was billed, what has been paid and what is still owed, every letter sent with its date, the escalation schedule with each stage's state, and what happens next and when.
Inputs: invoice (required), on.
Chase an unpaid invoice: generate the letter for the current stage of the ladder -- reminder 1 (polite), reminder 2 (firm, with the late fees note) or the final notice (before-action wording) -- as Markdown or as self-contained printable HTML. Nothing is emailed or sent anywhere: this server produces the letter text, and sending it is your act. Record the sending with letter_sent so the ladder advances.
Inputs: invoice (required), on, stage, format.
Record that a chase letter was actually sent, with its date, so the ladder advances to the next stage. Letters go out in order: reminder 2 cannot be recorded before reminder 1. Returns what is due next and when.
Inputs: invoice (required), sent, stage.
Turn Pro on for this connection with key, an MCPL1.. issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.
Inputs: key (required).
Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.
Inputs: no named parameters.
Every unpaid invoice past its due date: how many days late, what is still owed, which letters have gone out, and what is due next and when. Sorted by days late, worst first.
Inputs: on, limit.
Record money received against a chased invoice, in whole MINOR units: a part payment lowers what is still chased, a payment that covers the balance closes the ladder and frees the free-tier slot. Returns the outstanding amount.
Inputs: invoice (required), amount_minor (required), date, note.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Client statements of account, ageing of open invoices and payment chasers as text or PDF.
Find overdue invoices, draft invoices, and chase payment. Sends need your confirmation.
UK bookkeepers: chase clients for Making Tax Digital quarterly records, upload links, reminders.
Make an accounts receivable aging report from your open invoices and see who owes you money.
Add one secure layer between your agents and this server.