Stop clicking through Moneybird.
Tell your AI what to do.
Let your AI drive your Moneybird administration — and read your receipts with vision, better than Moneybird's own OCR.
Run your Moneybird in plain language.
Drafting and sending invoices, looking up contacts and bookings, and having your receipts read automatically — you ask for it instead of clicking through screens. The MCP server translates your request into Moneybird API calls, running locally on your machine. Your API token stays with you, no cloud middleman.
AI reads your receipts — better than Moneybird's own OCR.
Moneybird doesn't always recognise the fields on a receipt correctly. The MCP server fetches the receipt (PDF or photo), and Claude reads it with vision — amount, date, supplier, VAT. You check the proposal, and only then is it written back to Moneybird. Never automatically.
- 01 Claude requests your Moneybird receipts.
- 02 The receipt is downloaded and shown to Claude as an image (PDFs are rendered page by page).
- 03 Claude reads the receipt with vision and fills in the missing fields.
- 04 You review and approve the proposal in the chat.
- 05 Only then does the MCP server write it back to Moneybird.
What you can ask your AI.
Read this month's receipts and fill in the missing amounts.
The AI downloads each receipt, reads it with vision, and shows a proposal per receipt before anything is written back.
Draft an invoice for Smith & Co: 8 hours of consulting at €95/hour.
The AI drafts the invoice in Moneybird and asks for confirmation before sending.
Which invoices have been outstanding for more than 30 days?
You get an overview grouped by client, no filtering required.
What was my revenue in Q2, excluding VAT?
The AI totals the sales invoices and returns the figure.
What's in it now.
These operations are in it now. Missing one? Add it in the notes field below — we'll build it in.
- Receipts: reading with vision, correcting and writing back
- Invoices: drafting, sending, looking up
- Contacts: searching, creating, updating
- Products: looking up
- Generic escape hatch for any Moneybird API endpoint
Why EASEO.
We only build MCP servers we would run in production ourselves. Our WeFact MCP server already exists: runs locally, your API key stays on your machine, tested on a real administration. We hold Moneybird to the same standard. No cloud middleman, no telemetry.
Request early access.
The Moneybird MCP server is built and running; we're opening it up in phases. Leave your details and we'll give you early access.