Your business software,
run in plain language.
An MCP server lets your AI assistant work directly with your administration, invoicing or payments. We build them for Dutch business software — running locally, tested, your API key stays yours.
In short: EASEO builds MCP servers (Model Context Protocol) that let AI assistants such as Claude run your Dutch business software in natural language. The WeFact MCP server is on sale now; Moneybird, e-Boekhouden, Exact Online and Mollie are on a waiting list. Everything runs locally — your API key and data stay on your own machine. For other systems: bespoke MCP.
What is an MCP server?
Model Context Protocol is an open standard from Anthropic. It's the plug that lets an AI assistant talk to external systems safely. An MCP server is that plug for one specific system: it translates your AI's instruction ("send the monthly invoice") into the right API calls for your software, and translates the result back into a readable answer.
The difference with a chatbot that talks "about" your software: an MCP server lets the AI actually work in it — reading and changing data — with your control at every step. And because our servers run locally, your API key stays on your own machine.
Which software.
WeFact
Live — on sale nowAccounting & invoicing
Let your AI assistant run your WeFact administration. Local, tested, on sale now.
View productMoneybird
Private beta — request accessAccounting & invoicing
Let your AI drive your Moneybird administration — and read your receipts with vision, better than Moneybird's own OCR.
Request early accesse-Boekhouden.nl
In developmentAccounting & invoicing
Run your e-Boekhouden administration with your AI assistant, without clicking through screens.
Add me to the listExact Online
In developmentERP & accounting
Connect Exact Online to Claude and other AI clients for administration by dictation.
Add me to the listMollie
In developmentPayments
Look up and mutate payments, refunds and customers in Mollie through your AI.
Add me to the listNixfact
Our own productERP & invoicing
The MCP server for Nixfact — included with your Nixfact environment on nixfact.eu.
More about NixfactYour system
BespokeCustom work
Other software with an API? We'll build an MCP server for it. From €1,500 excl. VAT, after a short scoping call.
Request a bespoke MCP serverRunning more than WeFact?
Most businesses run three or four systems that don’t talk to each other. Which ones are worth connecting depends on how you work.
Local, tested, yours.
We only build MCP servers we run in production ourselves. They run on your own machine — no cloud middleman, no telemetry, no phone-home. Your API key stays in your own environment, never in our database. The WeFact MCP server is already there and auditable on GitHub; we hold every new integration to the same bar.
FAQ.
What exactly is an MCP server?
Model Context Protocol (MCP) is an open standard from Anthropic that lets AI assistants such as Claude talk to external systems safely. An MCP server translates your AI's instructions into API calls for your software — your accounting package, for example — so you can run your administration in plain language.
Why does EASEO build these servers locally?
Our MCP servers run on your own machine or VPS, not in our cloud. Your API key stays with you, we never see your data. That's deliberate: with administration and payment data, sovereignty matters more than convenience.
Which integrations come first?
Sign-ups decide. WeFact is already there. For Moneybird, e-Boekhouden, Exact Online and Mollie we're first measuring demand via the waiting list — the integration with the most sign-ups gets built first.
I use different software. Is that possible too?
Yes. If you work with a system that has an API, we'll build a bespoke MCP server for it. See bespoke MCP.
Which AI clients work with MCP?
Claude Desktop, Claude Code, Cursor, Zed and a growing list. Any MCP-compatible client works — you register the server once in your client's config.